> If you are going one-on-one, then you can just have the stack show
> your id, and use a different method (email, etc) to communicate that
> to the target.
>
"different method" (to get the IP) which we once used with the now defunct
Marionette (4 years ago) that DID rely on a known third server but very
"lightly" was:
Initiating chatter box "server" boots, logs onto the net and writes it's
(dynamically received) IP to a small text file at some known ISP host
machine's web site, containing nothing but it's IP,port, then goes into
listen mode.
"Client" side chatters boot up, uses http to get the unknown chat server's
IP sitting on the known ISP web site, and then starts talking directly to
the initiating chat machine. You can build on this to set up a "chat room"
that is not happening on any ISP's server. . .the ISP's server just serves
up the IP address of the chat server.
The initiating chatter box has a field that serves as the "chat room" and
users get that data fed back to them after each post. which is appended to
the field. The strategy worked like a charm, but Marionett's protocols were
horrifically slow and the app had a memory leak and kept locking up after
opening more then three sockets to chatters, we abandoned the whole project.
But this should blaze in MC. Some "traffic control" would be needed for a
full blown chat room.
> If you are looking for a more universal/large scale/robust/automatic
> system, then I would think you'd need to set up a server at a fixed
> address (in other words, not at your location) and set up the chat
> clients to automatically log in to the server, and find each other
> through that.
Hinduism Today
Sivakatirswami
Editor's Assistant/Production Manager
www.HinduismToday.com
www.HimalayanAcademy.com
[EMAIL PROTECTED]
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
