Yes Chris RMI is a pain in the ass and I have been trying to make a websocket client endpoint now. It however keeps closing and I am not to sure as of why right after the connection is open. http://stackoverflow.com/questions/26636452/tomcat-clientendpoint-websocket-keeps-closing has the code, asked the questions on there and have not gotten any answers. If you could you may look at the code and reply in this email chain why it keeps closing right after it opens. It is straight forward (as of what i know understand) my ignorance was due to being new to tomcat and websockets so sorry for any of that.
On Wed, Oct 29, 2014 at 1:47 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Jason, > > On 10/29/14 8:28 AM, Jason Ricles wrote: > > foo is not a webapp, it is a separate program running on the > > computer as a daemon. > > I understand that. I'm only suggesting that, since you have to > communicate with Websocket-speaking web application, maybe foo ought > to be a Websocket client of that webapp. > > > It has to do this stuff for it needed to be ran like this. bar is > > basically the gui to the daemon, providing what is happening on > > the machine to someone at another computer, since the machine is > > headless these programs are being ran on. > > So you have a data-collection program (the foo daemon) and an > aggregating / reporting program (the webapp). It seems like it would > be pretty simple to have the daemon push data to the webapp over > Websocket. Then your data consumers (themselves Websocket clients) can > get that same data pushed-out to them. > > Maybe I'm being naive, but this seems fairly straightforward to me. > > > So I am curious as to how having my foo program running outside of > > bar how it can interact using websockets? > > Grab the Tomcat Websocket client library and write your code to use it > for communication. Or use any other Java-based Websocket client > library. Or write your daemon in something other than Java and use > whatever Websocket library is available (Perl? PHP? C++?). > > > So far I have seen that they are disconnected and have no clue > > about each other outside of using RMI. > > RMI is a complete pain in the ass except under some very special > circumstances. It sounds like you might fit into those special > circumstances, so feel free to give it a try. > > If it were me, I'd do it all with Websockets: > > 1. Foo Daemon -> web aggregator > 2. web aggregator -> data consumers > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: GPGTools - http://gpgtools.org > > iQIcBAEBCAAGBQJUUSg8AAoJEBzwKT+lPKRYY9gP+wTNvdwerStWi8y5LMOS69UY > /GkYP+W9mW9Uxxq6eXs8zTGfJzMrVdp56Y0ywmzyj5PUdMPJBN9HSpn496/tQttF > qEjwaqXa6ZJe2Y5s0bAHPVnz2cP3aiNLWP+RlP8vF0tlccBWJFaG+9EC/4TEzJzZ > VdJm00EHre6LY9Muk+39PlonMqKCUb9hnkq/97CBjmur1UWtqlfeVBz305FudWXG > uZcpjgLpJ/ETK/Ui69Pyg9c1F4GFpK+rDpY2CQZdg9fUpGgg22iURlXWt14ueqSL > R6AH9Mvt1GrT88ZMBiTsYKWDCRBtxbTQ8Pgl16U0qRAFF8hSu2nJzKhtjdrwgQp2 > Yw4+SGmwEky8jmCUZhkCPg2Y8ds/l4NoK5s5V5ub7OOGPXaT8jHGanrEFM0wNqWX > bqZj10QvAN5Pvm2jJWjX+N1sSARWzDBuWfsQHvIcRihxvXr8UJNwCsYkZySCluXU > S1n9aoPi+Hx/yMPV5pMvtOsrRaDodyJFouDP6euKA4MV7dCs9ndcLCVL7Y8vDQ5f > Y/oExkPqMgWmjtd0Sg5DEDQvJgdzlwvKF1YNU1+bAZgpu05MlL+ybfpYfLUhmJsR > wJuzyFFmoP3Jr/GL9Cw1QNX/enPcJt2phPccXcTWW0uwg2KXCaYcNXzyCOAfzmsZ > ffRqiIneLm2io6yG1qhV > =xzLA > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
