Hi, >I still don't see how I have the servlet check back every so many ms for an >event or a status flag to be set without performing some sleep() or wait() >without burning CPU.
I don't get it. You don't want the servlet to return until it's done writing the web page, which means waiting for your async request to complete. But you don't want to wait, you don't ant to sleep, and you don't want to burn CPU. HTTP is a stateless protocol. One request = one response, with all the content. You can do stuff with JavaScript like posting a "request in progress" text and polling for the servlet to complete, but that's tricky and fragile. Are you looking for a client-side or server-side solution? Have you considered having the servlet use JMS for this, i.e. send a JMS message and block until its returned? Have you actually profiled a wait() or sleep() request to see that "it burns CPU?" You might be positively surprised... Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
