How to write an API for a Python application?

[Mike Meyer]

claird at lairds.us (Cameron Laird) writes:
> In article <1132233532.413086.7330 at f14g2000cwb.googlegroups.com>,
> Paul Boddie <paul at boddie.org.uk> wrote:
> 			.
>>meaning that callbacks and other things just work. Rolling your own
>>solution, on the other hand, can end in a long road discovering what
>>those CORBA people were doing for all those years.
>>
>>I suppose if CORBA is too heavy, there's always PYRO. I can't comment
> 			.
> Indeed, Paul:  those who scorn CORBA often *do* re-create it,
> poorly.
>
> I still don't think it's the right answer for Mr. Kshepitzki.
> Pyro might be perfect.  My own instinct is to start even more
> primitively, with a minimal asynchat client and server.  I've
> looked through the *Cookbook*, and see that it doesn't have
> what I want.  Maybe it's time Phaseit donate one of the
> little models we use ...  

CORBA includes an awful lot of things that probably aren't needed for
Mr. Kshepitzki's application. If the choice comes down to CORBA or
rolling your own at the socket level, I'll take CORBA. But there's
lots of room for other solutions in between those two. I've played
with the idea of a simple, single-connection protocol that would do
what he wanted, without all the excess. If someone had something
similar to that already written, it'd be great.

        <mike
-- 
Mike Meyer <mwm at mired.org>			http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.