When I first started in web page develompent I was using Java Servlets. One thing I remember coming up again and again was that rather than using strings to store your HTML, before dumping to the response object, was that you should use a stream.
Does this hold true for ASP?
I know that using strings to hold large amounts of text can be detrimental to performance. The building and tearing down of strings can cause huge performance hits on the page. Rather than always writing to the response stream (which I don't always want to do), I was wondering if it would be better to create a temporary stream, write to that and then dump it to the response stream when I was ready.
If this is a good way to go about it:
[ul][li]What type of stream should be used?[/li]
[li]Are there ways to tie the stream to the response object (ie.
sends to the response object)[/li]
[li]What are the advantages/disadvantages of doing something this way?[/li][/ul]
________________________________________
Nature and Nature's laws lay hid in night
God said "Let Newton be", and all was light
~Alexander Pope~
Does this hold true for ASP?
I know that using strings to hold large amounts of text can be detrimental to performance. The building and tearing down of strings can cause huge performance hits on the page. Rather than always writing to the response stream (which I don't always want to do), I was wondering if it would be better to create a temporary stream, write to that and then dump it to the response stream when I was ready.
If this is a good way to go about it:
[ul][li]What type of stream should be used?[/li]
[li]Are there ways to tie the stream to the response object (ie.
Code:
stream.flush
[li]What are the advantages/disadvantages of doing something this way?[/li][/ul]
________________________________________
Nature and Nature's laws lay hid in night
God said "Let Newton be", and all was light
~Alexander Pope~