Hi Horst,
Yes, this is the stuff I was trying to get to, thin/thick client/server, GUI's, application implementation approach, propriety/open/mixed standards, etc.

Mario


Horst Herb wrote:
On Thu, 22 Dec 2005 10:26, Cedric Meyerowitz wrote:

Mario each PC in a Doctors surgery is different and has different printers.
One has to tell BP which bin to use for what etc.  My own consutation room
has a printer with 3 bins.  One for scripts, one for letters & one for
Pathology / Radiology.


We have taken a different approach. All our printers have network interfaces, either built in or external print servers. Our practice software runs on one server only - both Firebird SQL server backend and GUI clients, and setups are *per room* - meaning the user logs into a "room", and then logs into the practice software as "user". Computers with known IP numbers log automatically into the correct room, but iof you take for example a laptop you would simply plug into the hub in that room, type "ssh -X <room>@<ourserver> <ourprogram> and it would launch the graphical user interface forwarded to your laptop, and it would use the printers configured for the <room> you logged into. The graphical user interface prompts you for your personal user name and password then.

This means we can use our server either from thin or from fat clients, but in any case, there is *nothing at all* to configure on the clients. We can use *any* computer with network card running *any* operating system that can run OpenSSH and X (is there any operating system that can't?) and it will always do what is configured on the server.

The server has an external SATA hard disk RAID system (bootable) containing evrything we need to run our practice network apart form the local print servers per room - meaning if we get a hardware failure on the server, we simply plug the SATA RAID box into any other machine with SATA port, boot, and we are running again, without having to reinstall or reconfigure anything at all.

Anybody can do that. Most people (including those who make a living from installing practice systems) simply don't know that this can be done, and those who know that it can be done rarely realize how *simple and cheap* it actually can be done. Visitors are welcome to my practice to see it in action and learn howto.

Horst
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk

_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk

Reply via email to