generic-library/libupnp
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merging trunk to branch 1.4.x

Browse Source 
git-svn-id: https://pupnp.svn.sourceforge.net/svnroot/pupnp/branches/branch-1.4.x@49 119443c7-1b9e-41f8-b6fc-b9c35fce742c
This commit is contained in:
Marcelo Roberto Jimenez
2006-07-08 12:38:45 +00:00
parent 062d62bbc4
commit 522dee807f
270 changed files with 9854 additions and 106 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
docs/dist/html/upnp/AboutCallbacks.html vendored Normal file
View File

@@ -0,0 +1,26 @@
<!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>