Re: Components for a client/server architecture

2007-05-22 Thread Irmen de Jong
John Nagle wrote: > You don't hear much about CORBA any more. It used to be derided > as a bulky way to marshall data, but then came XML. CORBA is much more than just a way to marshall data. GIOP (or its more often used implementation IIOP) is the marshaling protocolused in CORBA. And it is

Re: Components for a client/server architecture

2007-05-22 Thread John Nagle
Duncan Grisby wrote: > In article <[EMAIL PROTECTED]>, > Samuel <[EMAIL PROTECTED]> wrote: > > [...] > >>>Sounds like CORBA to me. CORBA has a very mature and good implementation >>>for Python called OmniORB, and interoperability with other orbs (the >>>ones available for e.g. Java) is very good

Re: Components for a client/server architecture

2007-05-22 Thread Samuel
On May 22, 3:10 am, Josiah Carlson <[EMAIL PROTECTED]> wrote: > That snippet of code shows that acquiring a lock does release the GIL. Of course, that does not mean that the (possible) issues no longer apply. However, I decided to hack up a quick prototype and see how it goes. If it doesn't work i

Re: Components for a client/server architecture

2007-05-22 Thread Duncan Grisby
In article <[EMAIL PROTECTED]>, Samuel <[EMAIL PROTECTED]> wrote: [...] >> Sounds like CORBA to me. CORBA has a very mature and good implementation >> for Python called OmniORB, and interoperability with other orbs (the >> ones available for e.g. Java) is very good - as CORBA as standard is >> ma

Re: Components for a client/server architecture

2007-05-21 Thread Josiah Carlson
Samuel wrote: > On Mon, 21 May 2007 12:06:50 +0200, Diez B. Roggisch wrote: > >> I'm not sure which configuration you want to change how often. But I'm >> not convinced that the python threading limitations really do make a >> difference here. Do you really benefit from multi-core capabilities in

Re: Components for a client/server architecture

2007-05-21 Thread Samuel
On Mon, 21 May 2007 12:06:50 +0200, Diez B. Roggisch wrote: > I'm not sure which configuration you want to change how often. But I'm > not convinced that the python threading limitations really do make a > difference here. Do you really benefit from multi-core capabilities in > this scenario? The

Re: Components for a client/server architecture

2007-05-21 Thread Diez B. Roggisch
> - Java (and possibly Jython) or Mono/C# (or possibly IronPython) on the > server. Requirements are: A strong and fair threading model. This is > actually what drove me away from Perl and what essentially prevents > using a normal Python interpreter on the server. I don't know whether > th

Components for a client/server architecture

2007-05-20 Thread Samuel
Hi, I am looking for some recommendations for client/server technologies and for the communication involved. I am currently planning to port a Perl application that has grown out of proportion to another language and architecture. For this purpose, I am investigating technologies that best fit