Absolutely - there is a problem, however, in that some fields include dynamic content that gets replaced prior to being sent. If these fields were encoded initially, it would create problems.
I'm sure I can think of something clever to cache as much as possible, though. -Mike On 2 Aug 2002 at 15:04, wr wrote: > Hi, > > the method "UrlConfig.getQueryString()" always generates the QueryString > from start. For every Thread and every Loop. This should be avoidable > since they are not changing after a run started. Inside URLEncoder gets > called twice. So wether URLEncoder itself is buggy or not we should try > to enhance performance in here by caching. Haven't thought that much > about it yet, though... > > What do you think? > > Wolfram Rittmeyer > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
