Communicate means something happens that the daemon is monitoring, so thus the daemon sends a message to the websocket server running on the webapp, so that message can get relayed to the webpage from the server and the daemon will also need to get messages from the webapp. It will then be two way and just regular messages.
On Tue, Oct 28, 2014 at 9:42 AM, chris derham <ch...@derham.me.uk> wrote: > On 28 October 2014 11:06, Jason Ricles <jgr...@alum.lehigh.edu> wrote: > > Ok so here is the problem I have been spinning my wheels on for day let > me > > just lay it out. > > > > I have a daemon written in java running lets call it foo for simpleness > on > > a linux machine that has the tomcat server running. On the tomcat server > is > > a WAR file for a webapp called bar. In that webapp is a webpage with > > JavaScript websocket communication that connects to a websocket server > that > > is also a part of the WAR file. So I have a webpage and a websocket > server > > communicating with each other. > > > > I want the foo daemon and the websocket server on bar (web application) > to > > be able to communicate with each other. Is there any way outside of > sockets > > to have foo and the websocket server on bar do this? > > Define communicate - what kind? One way, two way, what kind of data, > frequency, size, type? > > Chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
