🚀 go-pugleaf

In article <LOWRY.92Oct6120218@rotor.watson.ibm.com> lowry@watson.ibm.com (Andy Lowry) writes:

   And
   the problem with the typical software technology you see to support
   C-S style computing is that it's typically made fairly easy (but not
   nearly easy enough) to play the role of client, but much more
   difficult to play the role of server.  There's an asymmetry in the
   model, and there's an asymmetry in the implementations.  There appears
   to be a view (I've heard it enunciated several times) that servers are
   rare, and therefore it's not important to make them easy to create.

Could you explain more clearly about which "typical software
technology" you're talking about.

I've had experience creating servers for client-server pairs under two
different systems -- Sun RPC and SYBASE's Open Server (DB-Library and
Server-Library) systems.  Both of these systems provide a base which
makes it just about as easy to create the server as create the client
(although using Sun RPC directly is a bit hairy, using something like
rpcgen does indeed make the process about as easy as I've described).
SYBASE's Server-Library system also handles issues such as
multi-threading in the server almost transparently (i.e., the user
code has to worry about locking, semaphores, etc. where necessary, and
on some systems has to worry about occasionally yielding control in
long-running requests, but that's about it).

(Some of the words and phrases in the preceding paragraph are surely
copyrighted by someone.  So sue me.)

-- 
Jonathan Kamens                                         jik@MIT.Edu
MIT Information Systems/Athena              Moderator, news.answers
    (Send correspondence related to the news.answers newsgroup
        {and ONLY correspondence related to the newsgroup}
                 to news-answers-request@MIT.Edu.)