--- Steve Terrell <[EMAIL PROTECTED]> wrote: > Well, that's the thing. The HttpState will be > wrapped up in the > singleton. Some of the servers we support will allow > up to 32 > simultaneous threads of execution. How will that > work when all posts are > done via a singleton?
In addition to conceptual discussion, you might just want to go ahead and write a simple stress test, with N threads doing end-to-end requests against a simple server/service. You can also add artifical latency on server-side. And on client side, you can try out difference between singleton approach, and per-thread instance approach. Based on discussion so far, there's a good change there might not be significant difference either way; and specifically no significant benefit from non-singleton approach. However, if something was missing from problem description, this should prove the problem as well as perhaps also point the bottleneck (just profile on client side, and/or take thread dumps during test to see where locking is done). It's often a good idea to empirically try out approaches -- results are regularly surprising as intuition is not always best guide regarding performance and scalability. -+ Tatu +- ____________________________________________________________________________________ Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
