Authentication doesn't really belong here. You should either use an
authenticated transport (like HTTPS), or in the layer above (this is
what I'm currently doing).

On Oct 27, 8:54 pm, "Paul P. Komkoff Jr" <[EMAIL PROTECTED]> wrote:
> On 26 окт, 02:53, Alan Kligman <[EMAIL PROTECTED]> wrote:
> > I haven't had much to add recently. Protobuf-rpc is based heavily on
> > json-rpc, so there's really nothing new behind it. It works well for
> > my own use and is generic enough to probably work well for most other
> > people.
> > Is there a great deal of interest in devising a standard rpc protocol
> > definition?
> Yes it is.
> Since everything is trying to design its own RPC format, running into
> the same flaws as everyone else.
> For example, I haven't seen (in protobuf-rpc neither in protorcp) a
> single word about authentification.
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at

Reply via email to