Hi Nick, > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: None > To: [EMAIL PROTECTED] > Subject: [Jakarta Cactus Wiki] Updated: Cactus2Proposal > > Date: 2004-02-15T07:49:12 > Editor: 63.225.41.68 <> > Wiki: Jakarta Cactus Wiki > Page: Cactus2Proposal > URL: http://wiki.apache.org/jakarta-cactus/Cactus2Proposal > > no comment > > Change Log: > > ------------------------------------------------------------------------ -- > ---- > @@ -28,3 +28,4 @@ > > My preference goes to the Socket listener solution. I wish we could find > a way to make it work for multithreaded tests. -- VincentMassol > > +Why won't socket listener work for multi-threaded tests? --NickLesiecki >
How would it work? Maybe my wording is not right. Here's what I meant by "multithreaded tests": Imagine there are 3 tests executing simultaneously (test1, test2 and test3). Imagine that they are intercepted on the client side in the following order: test2, test1 and test3. How would the server side interceptor know the order of execution? If each test that executes passes its information to the server side, it's possible to run them concurrently. I'll change the wiki page to use "concurrent tests" instead of "multithreaded tests". Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
