|
|
  | Get started with SocketPro
A unique framework implemented with batching, asynchrony and parallel computation with online compressing
1. Requirements for client and server First of all, make sure that MS dotNet framework version 2 (or version 1.1) is installed at both client and server machines and runs properly because some of client and server samples are written from dotNet platform enabled languages. Note that you can skip installing dotNet framework if you do not do any dotNet-related development. 2. Two optional OpenSSL dlls If you want to build a secured socket to a remote server through OpenSSL, make sure that both client and server applications can access two OpenSSL dlls, libeay32.dll and ssleay32.dll. Usually, you need put the two dlls into your window system directory from the directory ..\bin. If you like to use MS SSPI to secure data, you simply ignore the two OpenSSL dlls. 3. Setups for SocketProAdapter If your development language is C/C++, make sure that your development environment includes the directory, ..\include. You may also meet compiling problem with the class CUQueue. If it happens, please install a Microsoft platform SDK no earlier than 2001 and your development environment use the SDK instead. At this time, you can use VC++ 6 and Borland C++ builder 5 or later to develop your C/C++ applications. You may need to add the source file sprowrap.cpp into your project for use of SocketProAdapter. If your development is based on .NET, you need to add both SocketProAdapter (SProAdapter.dll) and usocket.dll in the directory ..\bin into your client and server projects. 4. Play with tutorials At this time, SocketPro package is added with a set of tutorial projects for C++, C# and VB.NET. These tutorials comes with detailed step-by-step guides inside the directory ..\tutorials, which are very helpful for you to get started with SocketPro. 5. Setups for extra sample servers Inside the directory of ..\bin\, you will find two sample servers, TestSocketpro.exe and RemoteConnector.exe. The first one server is window console applications. To use it, just double click it. The console server application will run on the port 17000. The second one is a window NT service. After installing SocketPro, it will automatically run on the port 17001 if your machine runs on one of Win NT, 2000, XP and 2003 operating systems. For the sake of security, SocketPro installer program doesn't automatically configure remote window file service for you. However, you can configure it by yourself as below. First, go to registry HKEY_LOCAL_MACHINE\SOFTWARE\UDAParts\SocketPro\REMOTECONNECTOR\PlugIns\, and create a new sub key Module3. Under the key Module3, create one string value (Location) and set its value to ufilesvr.dll. Also, create a DWORD value (Param) and set it to 0. After restarting it, RemoteConnector will dynamically load the library and process all of win32 file management requests as shown in the following Figure. RemoteConnector also comes with a simple MS Access database file containing data such as user ID, password, service ID and granted services for each of user. It is easy for you to understand that RemoteConnector use the database to control accessing from different clients with credentials. Open the database file and see what it has. RemoteConnector comes with the C++ source code. See it inside the directory ..\samples\others\server\RemoteConnector\. 6. Others The SocketPro package contains a lot of traditional VB6 samples. If you are using VB.Net, you simply use Visual studio.net tool to convert them to VB.net code samples. Without registering SocketPro, a SocketPro server supports two socket sessions for free only. Otherwise, a SocketPro server will prompt a message to ask you for registering SocketPro. If so, simply click the message box and the SocketPro server will continue to run. After registering SocketPro by getting a proper key to unlock it, the message box will never appear again, no matter how many socket sessions are established. At client side, you will not get this message box. |
