Your approach sounds perfectly reasonable to me. What don't you like about it?
jk On Thu, Apr 09, 2009 at 10:36:39AM +0300, Cristi Manole wrote: > Hello, > > I have a wicket application where a user starts an action on another system > (different machine, outside network). I would like for this specific user to > receive a response from that system once the action is finished (it takes a > fair amount of time) and the status of that action. > > My idea is to have inside Wicket application an ajax self updating panel, so > that the database of the application gets read from time to time. The other > application would send a "message" to the Wicket application (call some page > with some page parameters), which would update the specific database table > with the user who started the action and the response. Once the action is > finished, the self updating panel (aware of this by reading it in the > database) becomes visible and it will contain that message to inform the > user. > > I think my idea is bad. If nothing else I consider it resource savvy. > > How do you guys handle communication between two applications (the other > application is not written in java) in order to provide the response to the > user without refreshing the page? > > Thank you very much in advance, > Cristi Manole --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
