[JDEV] Component Requesting All Packets

[Nicholas Perez]

Eh, it's their library. They can call it whatever they want and do 
whatever they want with it. Of course if people run away with the 
"misunderstanding" then I guess it was meant to be, and it will be the 
defacto standard (like so many other retarded technologies out in the 
world or word-to-company associations).

Peter Millard wrote:

>Trejkaz Xaoza wrote:
>  
>
>>On Fri, 6 Feb 2004 03:23, Peter Millard wrote:
>>    
>>
>>>Folks, realize that component protocols are SERVER IMPLEMENTATION SPECIFIC.
>>>So the library should NOT be named Net::XMPP, it should be named something
>>>like Net::jabberd2. Also components built using this protocol will not work
>>>other servers (ie, jabberd 1.4).
>>>      
>>>
>>That's true, but what's the point in putting an entire login procedure into a
>>package called Net::Jabberd2, when you will be putting exactly the same code
>>in for an XMPP client library? (i.e., they will both be using SASL.)
>>    
>>
>
>You don't understand... We're talking about components, not clients. I agree
>that ALL XMPP clients will use SASL, but we have no idea what various servers
>will use to connect up their components. It just so happens, that j2 uses SASL.
>Other servers may, or may not use it.. They could use something completely
>different, or they could just continue to use the protocol layed out in:
>    http://www.jabber.org/jeps/jep-0114.html
>
>pgm.
>
>_______________________________________________
>jdev mailing list
>jdev at jabber.org
>http://mailman.jabber.org/listinfo/jdev
>
>  
>