We're trying to build an app that sends a copy of all events
to another instance of the app. A collaborative app...
We now have this capability. We'd like to extend this
feature over the web using tunneling.
We are thinking of using a servlet to proxy the events to the
"on our side of the firewall" instance of the app.
Does this architecture makes sense? Someone told us that
a servlet cannot make a persistent connection to the (external)
app, so it would be very slow and exhibit "jerky" behavior. We'd
have to build some sort of polling mechanism to get devices using
servlets... which we'd like to avoid.
Any comments are appreciated. Thanks.
Frank G.
+======================================================================+
| Crossroads Technologies Inc, 55 Broad Street, 28th Fl, NYC, NY 10004 |
| Email: [EMAIL PROTECTED] Web: www.CrossroadsTech.com |
| Voice: 212-482-5280 x229 Fax: 212-482-5281 |
+======================================================================+
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
