| Groups | Blog | Home |
inetserver asp components : Concatenation help
Good day folks,
I finally broke down and wrote my first DLL to "secure" my asp code. One of the classes I wrote in the object contains many string lines. So I'm currently writing the code like this: Function myClass(variables) as string myString = myString & "......" myString = myString & "......" etc myClass = myString end function I'm just wondering if there is a better way to handle this. -- Thanks from this ASP Newbie
It depends. In some instances, you are better writing directly to the
stream: Response.Write AnotherString Response.Flush It depends on the amount of information you are concatenating. With components, you will have to get the ASP context, which is most easily pulled from COM+ (IIS runs under COM+ in Windows 2000 - NOTE: MTS is basically COM+ (minus some features) for Windows NT 4.0). If each string line is short, you are better concating the string. In general, a Response directly from the component is less expensive than outputting the string from the class and writing from ASP. With small strings, this is not necessarily true. One more note: Do not necessarily default to performance. Understandable code is far more valuable than code that saves a few milliseconds (at least in most applications), so consider maintainability in your equation. -- Gregory A. Beamer MVP; MCP: +I, SE, SD, DBA ********************************************************************** Think Outside the Box! ********************************************************************** [quoted text, click to view] "David P. Jessup" <davidATimntDASHtechDOTcom> wrote in message news:ecCo0ZpsDHA.2132@TK2MSFTNGP10.phx.gbl... > Good day folks, > > I finally broke down and wrote my first DLL to "secure" my asp code. > > One of the classes I wrote in the object contains many string lines. > > So I'm currently writing the code like this: > > Function myClass(variables) as string > > myString = myString & "......" > myString = myString & "......" > etc > > myClass = myString > end function > > I'm just wondering if there is a better way to handle this. > > -- > Thanks from this ASP Newbie > >
Thanks for the response Gregory. I guess I could have stated a few more
details in my original post. This particular class object is actually iterating through an array from a DB and building a table, with paging too. I guess I'll put some timings in and check against my original response.write in the original ASP before I moved it to my DLL. If the class is only writing a table with only one record I'm dealing with about 32 string lines that need to have concatenation done to them. But my experience with the in-house DB is that my users pull hundreds(sometimes thousands when users don't know how to delimit their SQL queries) of records at once and page through them. Again, thanks for replying so quickly, have a great day. -- Thanks from this ASP Newbie "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@comcast.netNoSpamM> wrote in message news:uAPxTopsDHA.1756@TK2MSFTNGP09.phx.gbl... [quoted text, click to view] > It depends. In some instances, you are better writing directly to the > stream: > > Response.Write AnotherString > Response.Flush > > It depends on the amount of information you are concatenating. With > components, you will have to get the ASP context, which is most easily > pulled from COM+ (IIS runs under COM+ in Windows 2000 - NOTE: MTS is > basically COM+ (minus some features) for Windows NT 4.0). > > If each string line is short, you are better concating the string. In > general, a Response directly from the component is less expensive than > outputting the string from the class and writing from ASP. With small > strings, this is not necessarily true. > > One more note: Do not necessarily default to performance. Understandable > code is far more valuable than code that saves a few milliseconds (at least > in most applications), so consider maintainability in your equation. > > -- > Gregory A. Beamer > MVP; MCP: +I, SE, SD, DBA > > ********************************************************************** > Think Outside the Box! > ********************************************************************** > "David P. Jessup" <davidATimntDASHtechDOTcom> wrote in message > news:ecCo0ZpsDHA.2132@TK2MSFTNGP10.phx.gbl... > > Good day folks, > > > > I finally broke down and wrote my first DLL to "secure" my asp code. > > > > One of the classes I wrote in the object contains many string lines. > > > > So I'm currently writing the code like this: > > > > Function myClass(variables) as string > > > > myString = myString & "......" > > myString = myString & "......" > > etc > > > > myClass = myString > > end function > > > > I'm just wondering if there is a better way to handle this. > > > > -- > > Thanks from this ASP Newbie > > > > > >
String Concatenation becomes exponentially more expensive as the string size
increases (apprx linear to 256k, exponential after that). There are a number of reasons for this (how OLEAUT32 caches BSTRs, Heap design), so for small strings, what you are describing should be fine. If you are doing a lot of strings, the string size is large, or if this is a high stress part of code, then you should use the mid() function within a loop to implement your concatenation. There are a number of string 'classes' out there that do this. You can refer to Hardcore Visual Basic for a good example. See http://support.microsoft.com/default.aspx?scid=kb;en-us;170964. Pat [quoted text, click to view] "David P. Jessup" <davidATimntDASHtechDOTcom> wrote in message news:%23DorA3psDHA.3436@tk2msftngp13.phx.gbl... > Thanks for the response Gregory. I guess I could have stated a few more > details in my original post. > > This particular class object is actually iterating through an array from a > DB and building a table, with paging too. > > I guess I'll put some timings in and check against my original > response.write in the original ASP before I moved it to my DLL. > > If the class is only writing a table with only one record I'm dealing with > about 32 string lines that need to have concatenation done to them. But my > experience with the in-house DB is that my users pull hundreds(sometimes > thousands when users don't know how to delimit their SQL queries) of records > at once and page through them. > > Again, thanks for replying so quickly, have a great day. > > > -- > Thanks from this ASP Newbie > "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@comcast.netNoSpamM> wrote in > message news:uAPxTopsDHA.1756@TK2MSFTNGP09.phx.gbl... > > It depends. In some instances, you are better writing directly to the > > stream: > > > > Response.Write AnotherString > > Response.Flush > > > > It depends on the amount of information you are concatenating. With > > components, you will have to get the ASP context, which is most easily > > pulled from COM+ (IIS runs under COM+ in Windows 2000 - NOTE: MTS is > > basically COM+ (minus some features) for Windows NT 4.0). > > > > If each string line is short, you are better concating the string. In > > general, a Response directly from the component is less expensive than > > outputting the string from the class and writing from ASP. With small > > strings, this is not necessarily true. > > > > One more note: Do not necessarily default to performance. Understandable > > code is far more valuable than code that saves a few milliseconds (at > least > > in most applications), so consider maintainability in your equation. > > > > -- > > Gregory A. Beamer > > MVP; MCP: +I, SE, SD, DBA > > > > ********************************************************************** > > Think Outside the Box! > > ********************************************************************** > > "David P. Jessup" <davidATimntDASHtechDOTcom> wrote in message > > news:ecCo0ZpsDHA.2132@TK2MSFTNGP10.phx.gbl... > > > Good day folks, > > > > > > I finally broke down and wrote my first DLL to "secure" my asp code. > > > > > > One of the classes I wrote in the object contains many string lines. > > > > > > So I'm currently writing the code like this: > > > > > > Function myClass(variables) as string > > > > > > myString = myString & "......" > > > myString = myString & "......" > > > etc > > > > > > myClass = myString > > > end function > > > > > > I'm just wondering if there is a better way to handle this. > > > > > > -- > > > Thanks from this ASP Newbie > > > > > > > > > > > >
See the following thread in microsoft.public.xml about benchmarking string
builder classes - there's even a couple of VB projects to download. Basically, *anything* is better than concatenation for anything beyond a few lines of text. http://tinyurl.com/wedq Cheers, Chris. [quoted text, click to view] "David P. Jessup" <davidATimntDASHtechDOTcom> wrote in message Thanks for the response Gregory. I guess I could have stated a few morenews:%23DorA3psDHA.3436@tk2msftngp13.phx.gbl... details in my original post. This particular class object is actually iterating through an array from a DB and building a table, with paging too. I guess I'll put some timings in and check against my original response.write in the original ASP before I moved it to my DLL. If the class is only writing a table with only one record I'm dealing with about 32 string lines that need to have concatenation done to them. But my experience with the in-house DB is that my users pull hundreds(sometimes thousands when users don't know how to delimit their SQL queries) of records at once and page through them. Again, thanks for replying so quickly, have a great day. -- Thanks from this ASP Newbie "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@comcast.netNoSpamM> wrote in message news:uAPxTopsDHA.1756@TK2MSFTNGP09.phx.gbl... [quoted text, click to view] > It depends. In some instances, you are better writing directly to the > stream: > > Response.Write AnotherString > Response.Flush > > It depends on the amount of information you are concatenating. With > components, you will have to get the ASP context, which is most easily > pulled from COM+ (IIS runs under COM+ in Windows 2000 - NOTE: MTS is > basically COM+ (minus some features) for Windows NT 4.0). > > If each string line is short, you are better concating the string. In > general, a Response directly from the component is less expensive than > outputting the string from the class and writing from ASP. With small > strings, this is not necessarily true. > > One more note: Do not necessarily default to performance. Understandable > code is far more valuable than code that saves a few milliseconds (at least > in most applications), so consider maintainability in your equation. > > -- > Gregory A. Beamer > MVP; MCP: +I, SE, SD, DBA > > ********************************************************************** > Think Outside the Box! > ********************************************************************** > "David P. Jessup" <davidATimntDASHtechDOTcom> wrote in message > news:ecCo0ZpsDHA.2132@TK2MSFTNGP10.phx.gbl... > > Good day folks, > > > > I finally broke down and wrote my first DLL to "secure" my asp code. > > > > One of the classes I wrote in the object contains many string lines. > > > > So I'm currently writing the code like this: > > > > Function myClass(variables) as string > > > > myString = myString & "......" > > myString = myString & "......" > > etc > > > > myClass = myString > > end function > > > > I'm just wondering if there is a better way to handle this. > > > > -- > > Thanks from this ASP Newbie > > > > > >
With small amounts of data (< 256k or so), you do not have a major problem.
Beyond that, you end up having to chunk out data (ie, Response.Write/Flush prior to hitting the 256k mark). This is most easily done by having the Response object write from the component. To set up the Response object, you will have to get Context, which is most easily pulled by making the component a COM+ component. This adds some benefits, but also adds a bit of weight itself. The weight is more than outputting a small amount of data, but less that concatenating huge strings. If this is not an option, moving to .NET is a good option, as the StringBuilder class gives you the ability to work with rather large chunks of text. Of course, you would more likely change methodologies and bind the data rather than chunk it out. -- Gregory A. Beamer MVP; MCP: +I, SE, SD, DBA ********************************************************************** Think Outside the Box! ********************************************************************** [quoted text, click to view] "David P. Jessup" <davidATimntDASHtechDOTcom> wrote in message news:%23DorA3psDHA.3436@tk2msftngp13.phx.gbl... > Thanks for the response Gregory. I guess I could have stated a few more > details in my original post. > > This particular class object is actually iterating through an array from a > DB and building a table, with paging too. > > I guess I'll put some timings in and check against my original > response.write in the original ASP before I moved it to my DLL. > > If the class is only writing a table with only one record I'm dealing with > about 32 string lines that need to have concatenation done to them. But my > experience with the in-house DB is that my users pull hundreds(sometimes > thousands when users don't know how to delimit their SQL queries) of records > at once and page through them. > > Again, thanks for replying so quickly, have a great day. > > > -- > Thanks from this ASP Newbie > "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@comcast.netNoSpamM> wrote in > message news:uAPxTopsDHA.1756@TK2MSFTNGP09.phx.gbl... > > It depends. In some instances, you are better writing directly to the > > stream: > > > > Response.Write AnotherString > > Response.Flush > > > > It depends on the amount of information you are concatenating. With > > components, you will have to get the ASP context, which is most easily > > pulled from COM+ (IIS runs under COM+ in Windows 2000 - NOTE: MTS is > > basically COM+ (minus some features) for Windows NT 4.0). > > > > If each string line is short, you are better concating the string. In > > general, a Response directly from the component is less expensive than > > outputting the string from the class and writing from ASP. With small > > strings, this is not necessarily true. > > > > One more note: Do not necessarily default to performance. Understandable > > code is far more valuable than code that saves a few milliseconds (at > least > > in most applications), so consider maintainability in your equation. > > > > -- > > Gregory A. Beamer > > MVP; MCP: +I, SE, SD, DBA > > > > ********************************************************************** > > Think Outside the Box! > > ********************************************************************** > > "David P. Jessup" <davidATimntDASHtechDOTcom> wrote in message > > news:ecCo0ZpsDHA.2132@TK2MSFTNGP10.phx.gbl... > > > Good day folks, > > > > > > I finally broke down and wrote my first DLL to "secure" my asp code. > > > > > > One of the classes I wrote in the object contains many string lines. > > > > > > So I'm currently writing the code like this: > > > > > > Function myClass(variables) as string > > > > > > myString = myString & "......" > > > myString = myString & "......" > > > etc > > > > > > myClass = myString > > > end function > > > > > > I'm just wondering if there is a better way to handle this. > > > > > > -- > > > Thanks from this ASP Newbie > > > > > > > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
| home · blog · groups | Questions? Comments? Contact the dn |