Sophie: libupnp-devel-1.6.6-2mdv2010.0 i586

libupnp-devel-1.6.6-2mdv2010.0.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<HTML>
<HEAD>
   <TITLE>typedef int (*Upnp_FunPtr)</TITLE>
   <META NAME="GENERATOR" CONTENT="DOC++ 3.4.10">
</HEAD>
<BODY BGCOLOR="#ffffff">

<H2>typedef int <A HREF="#DOC.DOCU">(*Upnp_FunPtr)</A></H2><H2>( IN Upnp_EventType EventType,<BR>&nbsp; IN void* Event,  IN void* Cookie )</H2><BLOCKQUOTE>All callback functions share the same prototype, documented below.</BLOCKQUOTE>

<A NAME="DOC.DOCU"></A>
<HR>
<H2>Documentation</H2>
<BLOCKQUOTE>All callback functions share the same prototype, documented below.
Note that any memory passed to the callback function
is valid only during the callback and should be copied if it
needs to persist.  This callback function needs to be thread
safe.  The context of the callback is always on a valid thread 
context and standard synchronization methods can be used.  Note, 
however, because of this the callback cannot call SDK functions
unless explicitly noted.

<P><PRE>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;int&nbsp;CallbackFxn(&nbsp;Upnp_EventType&nbsp;EventType,&nbsp;void*&nbsp;Event,&nbsp;void*&nbsp;Cookie&nbsp;);
&nbsp;&nbsp;&nbsp;&nbsp;</PRE> 

<P>where <B>EventType</B> is the event that triggered the callback, 
<B>Event</B> is a structure that denotes event-specific information for that
event, and <B>Cookie</B> is the user data passed when the callback was
registered.

<P>See <B>Upnp_EventType</B> for more information on the callback values and
the associated <B>Event</B> parameter.  

<P>The return value of the callback is currently ignored.  It may be used
in the future to communicate results back to the SDK.</BLOCKQUOTE>
<DL><DT><DD></DL><P><P><I><A HREF="index.html">Alphabetic index</A></I></P><HR>
<BR>
This page was generated with the help of <A HREF="http://docpp.sourceforge.net">DOC++</A>.
</BODY>
</HTML>