> -----Original Message----- > From: Nicholas Lesiecki [mailto:[EMAIL PROTECTED] > Sent: 29 November 2003 22:07 > To: Cactus Developers List > Subject: Re: [proposal] Cactus new vision (2) > > I'm all for the term "broker". What exactly does a broker do? I don't ask > so > much because I don't have a good general guess, but rather I want to hear > what are the common behaviors that every protocol will support.
- protocols: simply helper classes to transport information from cactus client side to cactus server side - brokers (or whatever term we wish to use): Ex.: Servlet broker, JSP broker, Filter broker, EJB broker, etc. A broker is there to execute a test case inside the container. It also defines the test case. For example the user-visible part of the Servlet broker is made of: ServletTestCase (and/or ServletTestSuite) + ServletRedirector. Brokers uses protocols to help transfer client-side brokering data to the server redirector. So protocols != brokers -Vincent > > Cheers, > Nick > -- > Nicholas Lesiecki > Software Craftsman, specializing in J2EE, > Agile Methods, and aspect-oriented programming > > Check out my books: > * Mastering AspectJ: http://tinyurl.com/66vf > * Java Tools for Extreme Programming: http://tinyurl.com/66vt > > Check out my articles on AspectJ: > * http://tinyurl.com/66vu and http://tinyurl.com/66vv > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
