David Yitzchak Cohen
dave at dave.tj
Fri Jan 10 13:19:23 CST 2003
On Fri, Jan 10, 2003 at 04:12:25PM +0200, Adrian Rapa wrote:
> >> We will use JEP-0025: Jabber HTTP Polling in order to do it.
> > Eeeek ... please don't use HTTP Polling if you don't have to. It's not
> > good.
> i'll take a look at this, also i want to be jabber compliant as it posible.
Jabber doesn't require HTTP polling ... standard TCP/IP streams work :-)
> >> I am thinking that the project has 2 parts:
> > definitely two parts, IMHO, is the way to go
> >> -- 1. Writing a server side jabber client that will conenct to jabber
> >> server when a new use logs in, and stores the data received from jabber
> >> server somewhere: in a file but it should exists database
> >> implementations
> >> too.
> > Make the server-side Jabber client persistent, so the web server only
> > sends the client commands. The Jabber client can maintain normal
> > (non-HTTP) connections to the Jabber servers in question.
> i dont quite understood this... can u give me more explanations... maybe
> an example
Basically, the same thing that a couple of other guys proposed, is what
I propose. You have a Jabber client on the web server where the "user
interface" is actually just a UNIX domain socket (and/or a TCP/IP port on
localhost), and then have your PERL/PHP/ASP/Python/whatever CGI-compatible
scripts connect to this jabber client every time the user wants to
do something. All the scripts have to do then is send queries ("user
wants to start a chat with dave at dave.tj" or whatever) to the back-end
jabber client and read responses ("create a new chat frame/window for
a chat with dave at dave.tj so the user can start chatting"), which makes
them extraordinarily simple.
Best of luck,
Uncle Cosmo, why do they call this a word processor?
It's simple, Skyler. You've seen what food processors do to food, right?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the JDev