Client/Server Architecture

The ParaLaw database is a Client/Server database providing improved reliability and performance. In a client/server database model, the workstation software does not connect directly to the database files. Instead, the workstations send requests to the ParaLaw "Server" program, which accesses the database files on behalf of the workstations to process their requests. This means that the "server" portion of ParaLaw is the only program that actually has access to your database files, thus providing better security, reliability, and performance.

 

Security

The database files only need to be accessible to the ParaLaw "Server" program. This means that you can leave the database files locked up on your server, where no one else can get to them. There is no need to "share" the database folder.

 

Reliability

Client/Server databases improve reliability because again, only the server is actually connected to the database files. This reduces opportunities for corruption from a power outage on the workstation or network breaks.

 

Performance

When you do a search in ParaLaw, the ParaLaw server processes the entire search. However, it only sends back to the workstation just the portions that it needs to fill your screen.

Example:

Say you do a search for all contacts that live in Atlanta, which results in 2000 matches. Your screen however only shows the first 30 or so matches, so this is what the ParaLaw server sends back to the workstation. If you page down, it then sends the next 30 and so on. So instead of burdening your network by sending all 2000 matches back to your computer, it only doles out the matches that appear on your screen as needed. This is why ParaLaw can still provide good performance even when running over a slower network connection such as the internet.