Re: Qpid .NET Strategy - Interested ?

2009-01-14 Thread William Henry
Hi Aidan, - Aidan Skinner aidan.skin...@gmail.com wrote: On Fri, Jan 9, 2009 at 2:27 AM, Cliff Jansen (Interop Systems Inc) v-clj...@microsoft.com wrote: My impression has been that WCF is purely an RPC abstraction. Does it offer traditional messaging semantics as well? Yes. For

Re: Qpid .NET Strategy - Interested ?

2009-01-14 Thread William Henry
Oh and one more point of clarity: Both ART and WCF are proprietary technologies albeit WCF being the defacto new std on .NET. ART is very niche and becoming less relevant. William - William Henry whe...@redhat.com wrote: Hi Aidan, - Aidan Skinner aidan.skin...@gmail.com wrote:

Re: Qpid .NET Strategy - Interested ?

2009-01-13 Thread Marnie McCormack
by changing a configuration file, in the same way a Java application can switch JMS providers without code changes. Cliff -Original Message- From: Aidan Skinner [mailto:aidan.skin...@gmail.com] Sent: Thursday, January 08, 2009 2:35 PM To: dev@qpid.apache.org Subject: Re: Qpid .NET

Re: Qpid .NET Strategy - Interested ?

2009-01-08 Thread Gordon Sim
Aidan Skinner wrote: On Thu, Jan 8, 2009 at 11:25 AM, Gordon Sim g...@redhat.com wrote: Marnie McCormack wrote: We have (to the best of my knowledge) no requriements spec for either implementation, functional or non-functional. I think the basic requirement for a client is to allow a user to

Re: Qpid .NET Strategy - Interested ?

2009-01-08 Thread Jonathan Robie
I'm interested. Jonathan Marnie McCormack wrote: All, We are currently in a somewhat interesting situation wrt to .NET clients in Qpid. I thought it might be helpful to get together the group of interested parties to agree the best way forward for the existing clients, and also to do some

RE: Qpid .NET Strategy - Interested ?

2009-01-08 Thread Cliff Jansen (Interop Systems Inc)
I would be very interested to join the conference call. Thanks. Cliff -Original Message- From: Marnie McCormack [mailto:marnie.mccorm...@googlemail.com] Sent: Thursday, January 08, 2009 1:53 AM To: qpid-...@apache.org Subject: Qpid .NET Strategy - Interested ? All, We are currently

Re: Qpid .NET Strategy - Interested ?

2009-01-08 Thread Robert Greig
2009/1/8 Aidan Skinner ai...@apache.org: I think System.Messaging is probably more relevant to .Net, this is the route that Mono has gone down with ActiveMQ and RabbitMQ: http://www.mono-project.com/SystemMessaging (there was also an attempt to implement it on top of our 0-8 client but that

Re: Qpid .NET Strategy - Interested ?

2009-01-08 Thread Carl Trieloff
Robert Greig wrote: 2009/1/8 Aidan Skinner ai...@apache.org: I think System.Messaging is probably more relevant to .Net, this is the route that Mono has gone down with ActiveMQ and RabbitMQ: http://www.mono-project.com/SystemMessaging (there was also an attempt to implement it on top of our

Re: Qpid .NET Strategy - Interested ?

2009-01-08 Thread William Henry
+1 re WCF. WCF makes it much easier. - Robert Greig robert.j.gr...@gmail.com wrote: 2009/1/8 Aidan Skinner ai...@apache.org: I think System.Messaging is probably more relevant to .Net, this is the route that Mono has gone down with ActiveMQ and RabbitMQ:

Re: Qpid .NET Strategy - Interested ?

2009-01-08 Thread Aidan Skinner
On Thu, Jan 8, 2009 at 8:39 PM, Robert Greig robert.j.gr...@gmail.com wrote: 2009/1/8 Aidan Skinner ai...@apache.org: I think System.Messaging is probably more relevant to .Net, this is the route that Mono has gone down with ActiveMQ and RabbitMQ: http://www.mono-project.com/SystemMessaging