On Thu, Dec 10, 2009 at 4:07 PM, Evan Jones <[email protected]> wrote: > On Dec 10, 2009, at 18:33 , Kenton Varda wrote: > >> client: "Open service Foo." >> client: "When request 1 is complete, call method Bar() on the result." >> > > I'm curious: Why have the Open request at all? Why not just "cal method > Foo.Bar()"? Are you planning on supporting some concept of "sessions"? >
Sorry, but I think you missed the whole point of the conversation. The idea is that when you make a connection (using my RPC system), you initially only get access to some "default" service. Typically that default service implements a method called Open() which returns references to other services. This way, the protocol itself does not need to have any concept of naming RPC services -- this can all be pushed to a higher layer. > > Evan > > -- > Evan Jones > http://evanjones.ca/ > > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
