|
Check the archives. Someone (several) on
this list has done extensive xmlSocket work, and I recall reading about an
actual product. I am going to be looking into this myself
soon. Tracy From: Thanks, Kevin! I finally did my
homework of the XMLSocket obj, but wasn't sure how to serve that protocol with
a web server or servlet container...I'll definitely look for the examples you
mention. I wonder if they are actual stand-alone, custom servers of if
they are a hack way of getting servlets to solve the problem. Thanks! Joey From: You probably want to look into the
XMLSocket object. This can make a connection back to a server and
maintain it. A 0 byte is sent between requests and response without
the connection being dropped. Those requests and responses are xml and
could be used for messaging or keep alives to avoid timeout issues. There
are some good Java examples out there on implementing this on the server end,
not sure about other platform implementations. Kevin From: All, We have, up until now, used webservices to check for
server-side notifications...we just poll (I know, I hate polling!). We'd
like to move to something more asynchronous, but I thought I'd ask the forum
for their recommendation. I know there is some kind of method in AS for making an HTTP
request...we could have a servlet that would accept that request, hold onto it
until some data comes in, and then finally respond to the request. Of
course there are probably time-out issues that would have to be side-stepped. That's about the only sol'n I can see being possible right
now. I'm not very familiar with RMI and Remote Objects, but can this
technology be used asynchronously in Flex? Any thoughts would be appreciated! Thanks.
|

