Howdy, >Im trying to create a servlet that is able to push back to the browser >rather than just operate a a pull mechanism. > > >To create this, there is a piece of javascript embedded within the html >outputted to the browser, so when additional javascript code is written in >at a later stage calling that function, that user can be notified of events >he is registered to.
You can have the JavaScript reload the page from your servlet, i.e. giving the servlet a new request. This is a common solution. >Perhaps not the way servlets were made to work but anyway! That's a big "but anyway" -- probably too big. >Unless you are able to come up with a better solution? Depends what your design goal is. A web server pushing stuff onto clients? Not my cup of tea, as you observed that's now how the web works. Clients requests, servlets (as their name implies) and more generally web servers (as their name also implies) serve. >How do i stop the response from ending then? I have left the html open at >the end so no /html code and I have not closed the output to the browser. Eventually, something will time out. The browser, the server, your firewall, many things can and will terminate the connection. Yoav Shapira 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]
