Re: [Xmpppy-devel] Upcoming major changes

[<mik...@yu...>]

Alexey,

I hope that you will be supplying a mechanism to return or find the raw socket object so that it can be used within an external select or poll. This will cause problems when trying to
manage a lot of connections or cleanly integrating with a GUI. If not, how do you expect these cases to be handled?

Thanks

Mike


On Tue, Jan 04, 2005 at 10:00:55PM +0300, Alexey Nezhdanov wrote:
> I'm now re-working some internal data representation in xmpppy library.
> The most visible changes will be (1) inaccessibility (in the old way) of 
> transport classes and (2) total transition from using Client class as 
> container to using Session class as container.
> 
> I.e.
> 1) you will not be able to access tcp/ssl socket directly:
> client.TCPsocket reference will not work anymore
> 
> 2) if you will need to access some sesion parameters that were stored in 
> client instance you should use session class instance instead.
> 
> Though I suppose that for most projects the changes should be completely 
> transparent or in the failure case just the search and replace job.
> 
> This will be the last serious changes in the 0.2 branch.
> 
> -- 
> Respectfully
> Alexey Nezhdanov
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Xmpppy-devel mailing list
> Xmp...@li...
> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel
>