Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!mit-eddie!bbn.com!fkittred
From: fkittred@bbn.com (Fletcher Kittredge)
Newsgroups: comp.windows.x
Subject: Re: X and RPC libraries: Can they co-exist?
Message-ID: <62280@bbn.BBN.COM>
Date: 24 Jan 91 03:05:34 GMT
References: <2962@hsi86.hsi.com>
Sender: news@bbn.com
Reply-To: fkittred@spca.bbn.com (Fletcher Kittredge)
Organization: Bolt Beranek and Newman Inc., Cambridge MA
Lines: 24

In article <2962@hsi86.hsi.com> wright@hsi86.hsi.com (Gary Wright) writes:
>
>Has anyone tried to integrate RPC mechanisms within the X toolkit
>event loop programming model?  I am looking specifically for anyone who
>has experience with Sun's ONC system or Apollo/HP/OSF's NCS RPC mechanisms
>with any X toolkit.  It doesn't seem to me to be a straight forward problem
>since both types of libraries (X & RPC) make certain assumptions about blocking
>on sockets reads and neither was designed with the other in mind.
>

OSF DCE comes with a threads package, which addresses this problem.  If
you don't have access to a system with DCE, then you could get help from 
a POSIX 1003.4a threads package, or a Mach C threads package.  I don't know
if Sun's ONC has a threads package associated with it. Sun's current thread
implementation will be of no help since it is a user space implementation
which blocks all threads if the current thread is waiting on a syscall.

regards,
fletcher

Fletcher Kittredge
Platforms and Tools Group, BBN Software Products
10 Fawcett Street,  Cambridge, MA. 02138
617-873-3465  /  fkittred@bbn.com  /  fkittred@das.harvard.edu