On Thu, 21 Oct 2004, Zerbe John W wrote: | uh... if you want your app to be "J2EE", and you want control over the | scalability of it, then yup, you want your servlet to accept the request, | queue it to an MDB and send back a "request accepted" reply. You could | potentially display a list of "batch" requests that are in progress with | the option to view the results of the one(s) that are finished.
My god.. How is it possible to suggest using such a nuclear warhead to shoot sparrows? Why not just fork a Thread, and do it there? Or use some Threadpool? I find this -nonsense- about the busy page having to be J2EE just annoying. -Consider- using J2EE in -seriously- heavy-distributed environments. Do not use even think about considering it to show a "request being processed" page!!!!! | | If not, then follow Nic's advice and write it in python! Really really strange how Python is able to do this w/o the full J2EE container using a MDB, then?? (Btw, that acronym reminds me of "MBD"..) | | Who'd have know it was that complex! hahaha! Endre ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
