Re: gpilotd & corba

[Manish Vachharajani <mvachhar vger rutgers edu>]

On Thu, 17 Sep 1998, Eskil Heyn Olsen wrote:

> On Wed, 16 Sep 1998, Manish Vachharajani wrote:
> 
> > I prefer the single select method though, unless servicing the CORBA
> > requests takes a long time, in which case threading is the only way to go.
> 
> Well, normally, I would even lt each corba request run in its own thread,
> but I have no idea of how effective that is under linux. Last time I used
> threads under linux, nothing worked, well, it worked as well as AIX, but
> thats about two years ago now.
> 
> What I am thinking about is, what is the amount of corba requests ? For a
> single user system, its probably real low, but I'd like it to be scalable,
> and if the gpilotd is to serve eg. 50 users, you could risk that your
> hotsync doens't gete throuhg for a couple of seconds. But then again, is
> that so bad as opposed to the risk of threadrelated errors/load of
> continously spawning threads ? 

Well is ORBit threads safe?
 
> However, when the gpilotd is to call the application via corba (for the
> notify system), that perhaps should be threaded, or the calls should be
> declared as oneway (maybe the best approach).

Probably have the calls be one way.

> I think I'll check how many locks are nessecary, if not too many, the
> corba part will run in a seperate thread. If too many, it will all be in
> one global select. And in both cases, the callbacks will be oneway.

What about the portability aspect?  The locks should be generic.  Also
what about switching uids on threads.  We MUST have this for security in
global gpilotd.



Manish Vachharajani
<mvachhar@vger.rutgers.edu>