Hi John, The server-side endpoint is itself implemented as a Tapestry 'service', allowing it to be injected into other application classes for pushing messages out to connected clients. Whereas the service injected into the endpoint class itself allows the endpoint to query this service when a client first connects, then send the client some data in the form of a message to be displayed on the client's UI.
The whole point of the mutual injection between these two services (the WebSocket being one) is to allow two way communication - push and pull. Regards, Chris. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
