[jdev] Gateways.. (snimmer, ircgate)
snakeru at gmail.com
Thu Nov 9 14:27:32 CST 2006
On Thursday 09 November 2006 22:36, Carlo v. Loesch wrote:
> Alexey Nezhdanov typeth:
> | Huh? You probably misread it. We have positive experience with serving
> | 800 simultaneous sessions with each sending and receiving messages every
> | second. And it was all running on the two accounts.
> oh i understand, so you can put some >400 sessions on each account.
No. Two accounts were not really needed. They were two because of another
reason. There is no limitation actually.
As long as accounts are different each time you can interconnect them using
only one mediator account.
So the logic is simple: there are 6G people on the Earth. So I can estabilish
3G sessions using only one mediator account (that is pure theory. In practice
I do not have such hardware available).
> we supported one account series per psyced process.. so it would be
> easier for us to just fork a couple...
> | Hm. Ok, that is possible way to go. But your solution is targeted as
> | 'chatting out' to other network while we targeting _receiving_ incoming
> | chat sessions from otherwise incompartible networks.
> i don't understand your subtle distinction. are you refering to the web
> interface? in our case if you're trying to make a chat session from a
> proprietary network you just need to know which screenname the gateway
> has and talk to it to get in touch with anybody in federation space..
Yes, that's it. In your case you know who you want to contact. I.e. you know
his IM system and screenname, passing it to gateway and become connected.
In our case you do not know who will connect you. You set up a trap on your
website put a meat and apples around it and sitting like a spider waiting for
the victim. They come, type in their IM system and screenname and got
connected to you.
So it is also anonymizer if you are honest enough to not write logs. You do
not know what IM system you was contacted from and they do not know where
their IM call landed.
More information about the JDev