Am Freitag, 7. März 2008 01:05:04 schrieb Jeff Pohlmeyer:
> On Thu, Mar 6, 2008 at 2:14 PM, Ingo Krabbe <ikrabbe.ask_at_web.de> wrote:
> > What I really need is contextual data, that I attached
> > to the callbacks and I need a signal when to create it,
> > when to change behaviour (in/out) and when to close and
> > destroy the contextual data, since that is completely
> > controlled by the asynchronous request:
>
> Does the "/curl/docs/examples/ghiper.c" example help you?
>
> In particular, the sock_cb() function manages GIOChannel
> objects inside a GMainLoop.

Yes, it at least helps to show what I mean.
Here SockInfo* is the contextual data. Actually you see here how SockInfo*
links back to the global information. Thats the same I do of course.

Still my critizism remains:

The same socket changes from OUT to IN while the SockInfo is created twice
with nearly the same information.

Also you did the same error as I did:

setsock in line 278 will never get called since it is detroyed by REMOVE
first !

Though I cannot prove it since I don't know in what context the ghiper.c will
be used !

>
>
> - Jeff

-- 
Mit freundlichen Grüßen / kind regards
I n g o   K r a b b e
System Administrator / system administrator
_________________________________________________________________________
Elements of Art GmbH         http://www.eoa.de
An der Eickesmuehle 22       41238 D-Moenchengladbach / Germany
fon: +49 (2166) 91567-3418   Registergericht: Moenchengladbach HRB 5855
fax: +49 (2166) 91567-99     Geschaeftsfuehrer: Erik Winterberg,
                                                Sebastian Leppert