After reading this for a while I cannot recall who asked for swing clients in the first place. I don't think they were ever a requirement.
In terms of non web stuff I would like to see something that could talk to JMS in an asynchronous manner but I'm not going to lose sleep if it's outside the scope. We have developed a somewhat webwork like Message EJB implementation which will do fine for the forseeable future. On Mon, 2003-01-13 at 20:20, Philipp Meier wrote: > I think we should keep swing clients out of the discussion at the > moment. Although I do not have very much experience with swing clients, > the design patterns differ from the request->response pattern of web or > rpc clients. So I see no problem in pushing the development slightly > away from the web to a more generic request->response pattern. > > -billy. -- Peter Kelley <[EMAIL PROTECTED]> Moveit Pty Ltd ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
