Section 2. loggernet sdk, 1 loggernet overview, 2 loggernet sdk overview – Campbell Scientific Software Development Kit Beginner's Guide User Manual
Page 9: 1 loggernet sdk controls
 
2-1
Section 2. LoggerNet SDK
2.1 LoggerNet Overview
LoggerNet is developed around client-server architecture. LoggerNet’s client-
server technology is based on a server that communicates with a network of 
dataloggers via various communications technologies. The server listens for 
client requests, accepts the requests, and acknowledges to the client that a 
request has been received. The server fulfils this request and returns 
information to the client. 
Often a client makes several requests. The server, however, processes only one 
request at time and in the order it was received. Once a client submits a 
request to the server, the client is free to do something else, knowing that its 
request will be processed. In other words, client requests may not get 
immediate response from the server nor do the clients have to stop doing 
something else while waiting for an answer. This is called asynchronous 
communication. 
2.2 LoggerNet SDK Overview
This software development kit contains six ActiveX controls and a limited 
version of the LoggerNet server DLL (CORALIB3D.DLL). A developer can 
use this SDK to create applications that remotely access an existing LoggerNet 
Server; however, the included LoggerNet server direct DLL can only be loaded 
and accessed locally. 
Installation of this SDK includes source code of examples written in Delphi 
6.0, Visual Basic 6.0, and Visual C++ 8.0 MFC that will start the 
CORALIB3D.DLL and use the other SDK controls. The install also includes 
documentation for developing applications using the methods and functions of 
the included SDK controls. Please note that the CORALIB3D.DLL can only 
communicate with a datalogger using a direct RS-232 or an IP Port connection 
and will not accept remote client connections. 
2.2.1 LoggerNet SDK Controls
The LoggerNet SDK controls simplify the task of application development 
tremendously by encapsulating complexities inherent in client-server 
communications. A summary of these controls and their uses is shown in 
Table 2-1.