Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <torriem@gmail.com>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.106
X-Spam-Level: *
X-Spam-Evidence: '*H*': 0.79; '*S*': 0.00; 'suppose': 0.07; 'from:addr:torriem': 0.16; 'from:name:michael torrie': 0.16; 'rebuild': 0.16; 'subject:GUI': 0.16; 'subject:library': 0.16; 'wrote:': 0.18; 'library': 0.18; 'example': 0.22; 'programming': 0.22; 'this?': 0.23; 'header:User-Agent:1': 0.23; 'header:In- Reply-To:1': 0.27; 'am,': 0.29; 'xml': 0.29; 'argue': 0.31; 'dropped': 0.31; 'layer': 0.31; 'another': 0.32; 'could': 0.34; 'basic': 0.35; 'but': 0.35; 'in.': 0.36; 'example,': 0.37; 'implement': 0.38; 'sometimes': 0.38; 'message-id:@gmail.com': 0.38; 'connections': 0.38; 'to:addr:python-list': 0.38; 'track': 0.38; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'space': 0.40; 'how': 0.40; 'course.': 0.60; 'simply': 0.61; 'provide': 0.64; 'answer.': 0.68; 'asynchronous': 0.84; 'dispatched': 0.84; 'premature': 0.84; 'regularly.': 0.84
X-Virus-Scanned: amavisd-new at torriefamily.org
Date: Tue, 28 May 2013 12:16:20 -0600
From: Michael Torrie <torriem@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.12) Gecko/20130105 Thunderbird/10.0.12
MIME-Version: 1.0
To: python-list@python.org
Subject: Re: Future standard GUI library
References: <mailman.1803.1368885785.3114.python-list@python.org> <20130522154233.fe5263cb231c375fc60c7c9b@gmx.net> <mailman.1967.1369232658.3114.python-list@python.org> <20130523174145.22a6c46f586b0a1f656d2412@gmx.net> <mailman.2020.1369324735.3114.python-list@python.org> <20130526194310.9cdb1be80b42c7fdf0ba502f@gmx.net> <mailman.2188.1369593244.3114.python-list@python.org> <20130528192655.08861babbd86e890634e6d90@gmx.net>
In-Reply-To: <20130528192655.08861babbd86e890634e6d90@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.2312.1369765006.3114.python-list@python.org>
Lines: 23
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1369765006 news.xs4all.nl 15970 [2001:888:2000:d::a6]:49567
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:46320

On 05/28/2013 11:26 AM, Wolfgang Keller wrote:
>> Please give me an example of a "suitable transport layer for a RPC
>> protocol". 		 	   		  
> 
> I won't give you an example, but just some very basic criteria:
> 
> - It must be very efficient for very small "datagrams"

I won't argue for XML here, but sometimes space efficiency is simply a
premature optimization.

> - It must provide connections

How would you do this?  Connections can and do get dropped regularly.
To rebuild connections you need another layer to track them.

> - For asynchronous programming it must provide for callbacks

What do you mean by this?  A transport layer has nothing to do with
callbacks.  All a client can do is make the call, and wait for the
answer.  The client library can make it look asynchronous of course.
And I suppose one could implement an RPC system using UDP where answer
packets are dispatched as they come in.