Skip to main content

EJB - GWT. Notificate GWT(javaScript) client about some events happened



I want to make document printing service using GWT(javascript+servlet) and EJB. What is the best way to cause EJB to notificate GWT client about some event is happened?





Of course, I can make it with using Timer (send request to EJB with some interval), but may be exist some more elegant way? (for example with callback, but I dont understand how to release it).





P.S.: I will use multitier architectur: JavaScript(GWT)+Servlet(GWT RPC)+EJB. And i working on document printing service (i want to notificate client that some file(s) is printed (also will be good if you give me advice of making progress bar)).





Thanks!


Comments

  1. You have multiple options:

    -Polling (e.g. using timer to send requests to the server)

    -WebSockets (server can directly notify the client about changes, but sockets aren't supported in IE family yet)

    -Some framework, which just magically does stuff for you (for example gwt-comet)

    Personally I would use polling, because may be it is slow and doesn't use server resources effectively, but it is the most stable one.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex