ebac5fe596
git-svn-id: https://pupnp.svn.sourceforge.net/svnroot/pupnp/trunk@45 119443c7-1b9e-41f8-b6fc-b9c35fce742c
27 lines
1.2 KiB
HTML
27 lines
1.2 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE> About Callbacks</TITLE>
|
|
<META NAME="GENERATOR" CONTENT="DOC++ 3.4.10">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#ffffff">
|
|
|
|
<H2> <A HREF="#DOC.DOCU">About Callbacks</A></H2></H2><A NAME="DOC.DOCU"></A>
|
|
<BLOCKQUOTE>
|
|
The Linux SDK for UPnP Devices contains functions that generate
|
|
asynchronous callbacks. To simplify the application callback functions,
|
|
these callbacks are executed on a thread owned by the SDK itself. The
|
|
SDK executes the application's callback function in a thread
|
|
context so the application can allocate memory and preserve the information
|
|
it needs. The application can also use standard thread synchronization
|
|
methods to ensure data integrity. Due to the possibility of deadlock, the
|
|
application cannot call back into the SDK during these callbacks
|
|
unless explicitly noted. There is no restriction in calling into the
|
|
operating system or any other application interfaces.</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>
|