I have a service implemented using Resource subclasses with a custom Finder subclass to instantiate the Resources. I noticed that if I make concurrent requests for the same URI, there is something before my Finder that is queuing the requests and dispatching them one at a time to the Finder. If the URI is different (but maps to the same Resource type) then the requests are processed concurrently.
Is this the intended behavior? I realize that Resources are not supposed to be thread-safe, but we should be able to process concurrent requests for the same resource as long as Finder.createResource() is called every time. Did I miss something? Thanks, Paul __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
