|
Vouch32 as Server |
|
Description |
| Vouch32 Server Protocol . v3.5 centers
around the SERVER concept where VouchSrv.exe is executed
independent of application as a server and client application's
requests are entertained by it on first-come-first-serve basis.
The necessity to develop SERVER protocol evolved due to few considerations, viz., 1) The complexity of functions responsible to execute some child process process through command-line parameters with different compilers. For example, Clipper provides RUN command, Clipper + Blinker provides SwpRunCmd() function, Xbase++ provides RunShell() function and (x)Harbour _Run() function. The behavior of all these is not consistent with each other. Also parameter passing is again a problem with them. Moreover, the behavior or these functions and commands is peculiar with OS to OS. With SERVER protocol, no RUN function or command is needed and hence renders Vouch32 more acceptable to any compiler comfortably. 2) Windows NT, 2000, XP operating systems do not release the child process until it is finished unlike Windows 98 or ME. This basic change in the behavior of Windows is not desired at times under Vouch32's underlying design and concept, where a client's request is desired to be terminated as soon as it is executed, to be run at the background. 3) OLEDB connectivity through ADO object to access various RDBMS servers, viz., Oracle, SqlServer, Informix, Sybase, MySql, etc., needs a different kind of functionality in order to use them in real-time environments. So a complete set of new functions are provided if Vouch32 is run as SERVER besides all previous functions which can be run under both protocols. To run Vouch32 as SERVER you need overall two code changes and one change in execution behavior: a) V32Init( cTitle, cServerPath, cConnectPath, cLibrary, lAsServer, cLinker ) . <lAsServer> need to be set to TRUE. b) VouchSrv.ini . Under [PATHS] section <VouchConnectionPath> must be set equal to <cConnectPath> of V32Init(). c) VouchSrv.exe is to be executed prior to any V32...() command is executed, but make it sure that VouchSrv.exe is NOT executed from within the application. VouchSrv.exe must be executed without any parameters. Once VoucSrv.exe is executed, Vouch32 icon will appear in the Windows Taskbar. Right-click on the icon will open the Vouch32Server window as below.
|
|
Vouch32Server Window |
|
|
Vouch32Server Window Controls |
| Started: Date and time
when Vouch32Server was started. Current: Current date and time Elapsed: Seconds elapsed since start and currents. Action List: Scrollable list of commands executed by the server with date and time. Log Book: When clicked, writes the contents of command list in <cServerPath>\VouchSrv.log file. Shut Down: Shuts down Vouch32Server. http://www.vouchcac.com : Activates the web browser and attempt to open my site where Vouch32 libs are hosted. http://www.vouch.ws/Vouch32/ : Activates the web browser and leads to Vouch32 dedicated support web-board which addresses your day-to-day questions.
|
|
Functions Usable Exclusively with Server Protocol |
| V32AdoSvOpen( cConnectionString ) ->
nConxn V32AdoSvDbf( nConxn, cSql, cDbf, aStruct, aProgBar ) -> nRecords V32AdoSvAry( nConxn, cSql, aProgBar ) -> aRecords V32AdoSvRec( nConxn, cSql ) -> nRecords V32AdoSvExe( nConxn, cSql ) -> lSuccess V32AdoSvClose( nConxn ) -> lSuccess |