Re: [Xmpppy-devel] Upcoming major changes

[Alexey N. <sn...@pe...>]

=F7 =D3=CF=CF=C2=DD=C5=CE=C9=C9 =CF=D4 =F7=D4=CF=D2=CE=C9=CB 04 =F1=CE=D7=
=C1=D2=D8 2005 22:40 mik...@yu...=20
=CE=C1=D0=C9=D3=C1=CC(a):
> 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?
These changes are targeted to itegrate poll() into the library and remove=20
select() calls (to allow override 1024 user barrier) so the requested=20
interface will definitely be provided.

> 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.

=2D-=20
Respectfully
Alexey Nezhdanov