[JDEV] JIT - ICQ Transport release

[lukasm]

admin at jabber.fsinf.de wrote:

>On Tue, 26 Nov 2002, Matthias Wimmer wrote:
>
>  
>
>>>Why are too many ports bad?
>>>      
>>>
>>1. scalability (you can have at most 65535 listening sockets per IP)
>>2. security
>>    a) Managing of firewall in front of the server
>>    b) outgoing connections to the ICQ-server are less vulnerable then
>>to listen for incomming connections that can be established by any
>>internet host
>>    c) harder to keep track on what is going on
>>    
>>
>
>That's true. However, one can run the transport on a machine not
>firewalled and/or limit direct connections to outgoing direct connections
>(which work fine, too. Machine looks like NATted then. As soon as the
>NATted machine messages a non-NATted one, a direct connection will be
>established).
>
>libicq2000 seems to support disabling incoming direct connections
>(Client::setAcceptInDC(bool d)) without sacrificing direct connection
>functionality completely.
>
Yes. Adding DC is very easy.

>
>But AFAICS JIT uses a rather heavily modified libicq2000 without sigslots
>and all that?
>
NO. Changes are only in I/O layer and I removed very slow sigslots.
JIT has all I/O in one thread. It is very safe and stable. I have JIT 
version on jabber with modules, and
I can have all modules: jsm, xdb + JIT on one jabber.

>
>Regards
>
>_______________________________________________
>jdev mailing list
>jdev at jabber.org
>http://mailman.jabber.org/listinfo/jdev
>
>  
>