Lonk,
I have a couple of KF-Socket apps! (and not games, either!)
One is a client that runs on workstations and allows the help desk to make queries to the system to obtain information about hardware, installed software, services, and processes. It's an enhancement to the System Interrogation Tool that radically improves performance. SIT will attempt a socket query to the listener on the client. If it can't successfully negotiate a connection, it drops back to authenticated WMI queries. A full WMI query over the LAN could take 20-30 seconds, but the KF Socket based listener reduces this to under 2 seconds.
Another is an app that synchronizes directories between a master and multiple secondary servers. The secondary servers make a connection to a listener on the master server, who - after a successful negotiation, will spawn a copy of the Unison file sync software, listening on a defined port. It will then respond to the client, reporting a successful service start on a specific port. The client then establishes the sync with the specific Unison listener. We've used this in syncing web farm servers as well as keeping documents sync'd with servers around the globe. We chose Unison because we could sync with Linux systems running SAMBA, and the client adapted to run natively in Perl. The Kix/KF service allowed the master server to only run the Unison sync apps when needed, minimizing the load of having one Unison app per remote server.
Glenn
_________________________
Actually I
am a Rocket Scientist!
