Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!portc01.blue.aol.com!news-peer.gsl.net!news.gsl.net!howland.erols.net!blackbush.xlink.net!ins.net!heeg.de!hmm
From: hmm@heeg.de (Hans-Martin Mosner)
Subject: Re: VW2.5 & RPC
Message-ID: <E0pBJK.Mrp@heeg.de>
Sender: uucp@heeg.de
Organization: Georg Heeg Objektorientierte Systeme, Dortmund, FRG
X-Newsreader: TIN [version 1.2 PL2]
References: <01bbcdf3$70e4a400$e7117fcf@martines.frontiernet.net>
Date: Mon, 11 Nov 1996 10:23:44 GMT
Lines: 27

Candace or Eduard Martinescu (martines@frontiernet.net) wrote:
: Hello,
: 	I was wondering if anyone has any experience with use smalltalk as an RPC
: server?  More specifically, as a DCE RPC server? Will their be problems
: because of DCE requirement for POSIX threads?

: 		Thanks for any information,
: 			Ed Martinescu

We don't have experience with DCE RPC but with Sun RPC server/client
software that we have written vor Smalltalk (VisualWorks).
It's actually quite easy to write servers in Smalltalk since you
get a reasonable thread model with the class Process. Unless your
server actions are lengthy, living with non-preemptyively scheduled
processes is not bad.
I don't know what the DCE requirement for POSIX threads means
in practice, though. I think that an RPC interface specification
must not specify how the server works internally, only that it
exhibits some externally visible behavior.

Hans-Martin

--
+--- Hans-Martin Mosner ---- Senior Smalltalk Guru :-) ---+
| These opinions are entirely ficticious.  Any similarity |
| to real opinions is purely coincidental and unintended. |
+--- <hmm@heeg.de> ------ URL:http://www.heeg.de/~hmm/ ---+
