[Linux-ha-dev] Re: [Fwd: Re: [Fwd: Re: draft of updated GRITS note]]

[Chris Wright]

> > > I think you are too frightened by the parsing/reply overheard of http.
> > > It really is pretty trivial. The point for me is that everybody knows
> > > it and is comfortable dealing with it.  Writing another
protocol/message
> > > format on tcp is novelty we should avoid, I think.  The real race for
> > > would seem to be amongst http, https, sun rpc, and corba, and even I'm
> > > willing to write off corba.  Given the complexity of doing sun rpc on
> > > Windows, I'm personally inclined to think that http/https are the
> > > best available choices.  I'm waiting for someone to try to convince
> > > me otherwise.
> > 
> > What about the RPC protocol from OSF. This can be used from just about
> > all of the major platforms.
> 
> That's DCE, right?  While it's available for most platforms, I don't
> know that it is trivial and plausible to implement cheaply on an 
> embedded platform that isn't already running free software.  I think
> I'd rather have raw tcp than DCE.

What types of embedded platforms are you thinking of, are these platforms
going to have any way to install this new application?  For example,
something like Network Attached Storage doing NFS...sure they support RPC as
part of NFS, but there is no way to add another RPC server to the NAS device
itself.

Somehow, it seems to me that the _actual_ messages being passed via the
GRITS verbs are more important than the transport protocol.  All I can say
is... do we really want to do our own data marshalling?

-chris