Tom Carter

Server And Client Software

My server software is actually a Message Switching system and includes an application layer for processing and routing incoming transactions. This software is written in C and runs under virtually any version of Unix or Linux and is very reliable, providing uninterrupted service over 99% of the time. Sun's Solaris is my referred version of Unix.

The server software is composed of multiple (limited only by system resources), co-operating processes. Fast and efficient interprocess communications and sychronization facilities allow the software to support a very large number of concurrent users and interfaces. The Dial-a-Cab Taxi Dispatching System supports well over 150 local and remote users as well as 1500 mobile users.

A main process contains executive level functionality and includes its own prioritized task scheduling and timer mechanisims. This main process centralizes the control of all connected devices and performs most of the "transaction processing" and "data routing" functions.

Each interface is a separate, child process that controls one or more physical devices or performs some special operation or function. Interface process failure is detected and corrected by the main process.

My server software supports Active Server Pages, making it a custom Application Server platform.

My client software is the user's interface to the server. This software generally resides on a Microsoft Windows platform and is usually written in Visual Basic since the GUI is great and the coding is fast and simple and fairly easy to modify, enhance, and maintain. I like to connect the local users via network sockets for the speed and reliablility but I also use other methods to make this connection.

See the Mobile Applications page for information on my mobile software.

A Sample System Description

My Dial-a-Cab Automated Taxi Dispatching system is Solaris based and runs on a Sun E3000. This system services approximately 80 local, Visual Basic based PCs doing Call Taker and Supervisory functions as well as database maintenance. There are also 75 Internet connections for the remote entry and tracking of trip information by Dial-a-Cab's preferred clients and an unlimited Active Server Page interface for trip entry by the general public. There are 8 radio channel interfaces supporting over 2000 mobiles that freely and automatically roam from one channel to the next. Four Mapping Station interfaces are supported to show, on demand, a taxi's location and eight Telephone system interfaces are used to automate customer call-backs. This system runs 24 hours a day, every day of the year, is over 99% reliable, and requires no operator intervention.

Server Software Features:

Computer Interfaces


I use computer interfaces to exchange data between one or more connected computer systems.

My interfaces operate in either client to server or peer to peer configurations.

Interface types:

  • Socket Connection
  • Serial Port Connection
  • Modem Connection (Dial-in/Dial-out)
  • SNA (LU 6.2)

Client Interfaces


Client interfaces may be fixed or mobile.

My client software is usually Windows based and written in Visual Basic.

When using Active Server Pages, I prefer Microsoft Webclasses and Javascipt.

Interface types:

  • Socket Connection
  • Serial Port Connection
  • Modem Connection (Dial-in/Dial-out)
  • Active Server Pages
  • Various RF Protocols
  • CDMA
  • CDPD

Automated Phone System Interfaces


Most companies have an automated telephone system used to route calls.

Many of these systems are able to be directed by a connected server system.

In general, the server system instructs the automated telephone system to:

  • Dial a specified telephone number.
  • If not connected, return the reason.
  • If connected, play a specified recording.
  • Collect keyed data from the connected party.
  • Return the collected information to the server.

The benefits are obvious. A physical operator is not required.

Calls handled in this manner are actually faster, cheaper, and more efficient than a physical operator.

Other Features


Other features included in my Server software include:

  • Hot Standby with Automated Takeover Capability.
  • Automatic System Crash Recovery and Restart.
  • Classic Store-and-Forward.
  • Configuration of Devices and Interfaces.
  • Configuration of Transaction Routing.
  • Database Synchronization During System Restart.
  • Prioritized Message Queuing.
  • Prioritized Transactions.
  • Pager and/or Email Problem Notification.
  • Well Defined Interface Implementation Methodology.
  • Well Defined Transaction Implementation Methodology.
  • Automatic Device and Interface Logging.
  • Automatic System/Application Exception Logging.
  • Automatic Logger Maintenance.
  • Dynamic Device and Interface Control (Open, Close, Restart)
  • Support of Many Mobile Data and Wireless Interfaces.
  • Support of Many Computer Interfaces.
  • Location Mapping Support.
  • Application Software Maintenance and Download. (see the Mobile Applications page)
Introduction Mobile Software

Comments /Consult/reliable-net/Tvc_host.html


Add your comments

Related Articles

Have you tried Searching this site?

Please read this disclaimer

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

/Consult/reliable-net/Tvc_host.html copyright Tony Lawrence All Rights Reserved

Views for this page
Today  This Week  This Month  This Year   Overall
5919254616
Paid Advertisers

Cingular cell phones  -  Advanced Cisco Networking and Security by Vinci Consulting  
Data Recovery Software  -  Internet Advertising  -