I keep forgetting what forum I'm in here -- I mostly use Swing, not HTML
browsers, with Struts, etc. This makes it a lot easier for me to use
whatever protocol I want for whichever service. If you are stuck using
an HTML browser as your vehicle for a user interface for the messaging
system, you
XMPP and HTTP are nothing alike. XMPP is a stateful protocol and HTTP is
a stateless protocol. XMPP pushes out alerts actively while with HTTP
you have to poll when doing messaging. XMPP is all XML (and extendable)
in addition. If you are going to use XMPP (and you should, instead of
hacking a
If you have to embed it in your site, and in your site only, forget about
sockets, xml and other "complicated" staff.
3 actions (getmessage, sendmessage, checkmessage) 2 html pages, a bit
javascript (for reloads) and
5-10 classes on the business logic will be enough.
Don't make things unneccessa
If you have to embed it in your site, and in your site only, forget about
sockets, xml and other "complicated" staff.
3 actions (getmessage, sendmessage, checkmessage) 2 html pages, a bit
javascript (for reloads) and
5-10 classes on the business logic will be enough.
Don't make things unneccessa
4 matches
Mail list logo
