On Fri, 10 May 2013 09:31:55 +0900 (JST) yamam...@valinux.co.jp (YAMAMOTO Takashi) wrote:
>>> +class Client(object): >>> + """a convenient class for a pure rpc client >>> + *sock* is a socket-like. it should be blocking. >>> + """ >> >> I'm not sure about having pure 'Client' class. Both end can be client >> and server once a connection is established. > > i think a pure synchronous client is at least one of common usages. > it's anologous to RyuApp's send_request. > if it turns out that there's no users of this, we can remove it later. I'm fine with having such function. My question is why we need two classes, Client and Server? ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
