Sockets are not currently supported from within a compute node application. Currently the only way to get data from the compute partition to the outside world is through the file system. In the near future, compute node applications will have the ability to communicate with the service partition (and other compute node applications) through an MPI-2 interface.

This is a bug in Windows 95. Resources are not properly reclaimed when a socket is closed. See the microsoft web site for a patch. (http://www.microsoft.com/)

Using sockets with Soar is not well-documented, but it has been done numerous times. Socket communication is included in the Eaters and TankSoar applications (which come with a tutorial document) and sockets have also been implemented with C code using a library written at Michigan called SocketIO. Eaters and TankSoar and the Soar 8 Tutorial are available on the Soar "Getting Started" web page, and SocketIO can be found near the bottom of the "Projects/Tools" web page. Soar 8.

These questions have more to do with the networking facilities you have available than they do with C.

A11) On UNIX (at least Linux), asynchronous sockets are not generally available, although you can arrange to get a signal when "any fd" is ready (FIOASYNC). If you're on windows, and you're prepared to deal with the significant management overhead, they can lead to good performance.

Dry socket is a bio-film problem and therefore there is no reason why it should not be treated by ozone.

All of these questions are outside of the scope of this list and have much more to do with the networking facilities which you have available than they do with C. Good books on the subject are Douglas Comer's three-volume Internetworking with TCP/IP and W. R. Stevens's UNIX Network Programming. There is also plenty of information out on the net itself, including the ''Unix Socket FAQ'', and "Beej's Guide to Network Programming".

Secure Sockets Layer (SSL) securely encrypts the information that is being sent over the Internet. Verified by Visa uses SSL to securely transmit data, but also adds another very important layer of protection by confirming the identity of the Visa cardholder during the transaction. This authentication process creates a virtual card present environment.

IntraWeb when deployed as ISAPI can be used with SSL by using the SSL features of the hosting Webserver. When deployed in stand alone mode, IntraWeb can also support SSL. However, some countries disallow the use of strong methods of encryption. It depends on the location where the application is to be run. Atozed Software does not provide any rights or licenses to use strong encryption methods.

Intel’s new processors are discussed below. Please see the chart for a side-by-side comparison of the different processors and sockets. Celeron M – Developed as an economical solution for the Pentium M, it was originally compatible with socket 479. However, two new types of Celeron M processors have recently been released by Intel. These are not compatible with previous versions and will not work on mainboards that use the older Celeron M processors.

HexTcpQuery directly uses the Windows Sockets API. So do all other HexGadgets except HexIcmp, which wraps the ICMP.DLL API.

Yes. There are two different categories of PhysioToolkit code, and the rules for using them are slightly different. The WFDB library is free under the GNU Lesser General Public License (LGPL). The LGPL permits you to use (or sell, or give away) the library with your own code. The only significant restriction is that you must make the sources for the library itself freely available. You do not need to disclose the sources for your own code simply because you have used the WFDB library with it.

No, but we encourage you to use the form. It will help you submit a complete and accurate application.

Yes, of course! However, while Dapper is in beta, there is no gaurantee that the service will remain available at all times nor any promise that new features and changes to the software won't break your software. That said, we'll make every effort to prevent disruption.

To use the vanilla Win32 winsock, you just need to #define __USE_W32_WINSOCK and #include "windows.h" (or "winsock2.h" at the top of your source file(s). You may find it easier to add "-D__USE_W32_WINSOCK" to the CFLAGS settings in your makefile, if you are using one, as this will then apply to all your source files.

On average there is a socket every meter depending on the Studio you choose but there are more than enough.

Yes. Toolkit implements the standard sockets API, based on the native Win32 Winsock 2.0 libraries (this is standard with Windows NT and Windows 2000, and distributed as part of the NuTCRACKER Platform on Windows 95/98). Toolkit sockets are semantically the same as UNIX sockets, including support for out-of-band data and asynchronous I/O notification. Toolkit does not, however, support the TLI or XTI networking APIs.

Solder contamination is the leading cause of socket failure. A small amount of solder is transferred to the socket contacts each time a device is inserted. These layers of solder oxidize, and cause contact resistance to increase. Eventually, the signal fails.

When I get tired my eye sockets get hot. And the more tired I get, the hotter they get. Does this happen to anyone else? (BTW, I'm trying to win a bet with my husband on this - your help is appreciated.) People with medical conditions that need them to sleep in a particular position usually use adjustable beds. These beds may also be used by people who are temporarily or permanently bed-ridden, to enable them to sleep peacefully.