Your
question raises some interesting issues about the limitations of the web
server-client relationship. Ideally, what you need is a classic "publish and
subscribe" paradigm (which is what this servlet mailing list is really,
except its using email), but this isn't how web clients and their hosts
work together - its more like "ask me a question, and I'll (try to) tell
you the answer, but if I don't find it till later, you'll never know!!", which
is hardly a satisfactory solution, if one at all, but hey, it cheap and easy to
develop and deploy! An alternative is to have a special network listener (a
web server is a glorified listener, but one that only operates "on demand") that
maintains continuous communication with its clients, even when there's nothing
to "say", which is expensive on network resources, so there's the downside, but
doable. Maybe you need to think instead about EJB's and RMI
(since Java doesn't support the function pointers that would allow
a callback function between (say) a C++ client and an RPC to a remote
host)...good luck!
|
- Sending Response Objet to client without reques... [EMAIL PROTECTED]
- Re: Sending Response Objet to client witho... S Srinivas Nayak
- Re: Sending Response Objet to client witho... subzero
- Nullpointer on dispatcher Peter Maas
- Re: Sending Response Objet to client w... Neelakantan Lakshminarayan
- Re: Sending Response Objet to client witho... Galbreath, Mark
- Re: Sending Response Objet to client w... Mike Silvers
- Re: Sending Response Objet to clie... APL
- Re: Sending Response Objet to ... Daniel Joshua
- Re: Sending Response Objet to ... Michael Weller