Hi,
Howdy!
Nick has started a unique id generator to support execution of concurrent cactus tests. However, there might be a better solution: return the test result in an HTTP header in the same HTTP response.
There might be issues with this solution. I think that I had some doubts about this in the past but I can't recall any good reason right now... :-)
How would we pass an exception thrown on the server side back to the client? That's really the only reason I see why we have two requests currently.
If it works, it will solve several issues: - prevent 2 HTTP requests which will be faster - support use cases where people using cactus have a load balancer (the second request to get the test result is balanced on another server)
If two requests are made with the same session, they should get processed by the same server (a spec requirement IIRC). So we could also maintain the session (if created) between the two requests.
- allow concurrent test execution
Which would also be enabled by using unique test IDs, of course.
-chris
What do you think?
Thanks -Vincent
-- Christopher Lenz /=/ cmlenz at gmx.de
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
