[rabbitmq-discuss] Rabbit crash, new persister

[Alexis Richardson]

Thanks Mark!



On Mon, Jun 21, 2010 at 4:10 PM, Mark Pollack <mpollack at vmware.com> wrote:
> Hi,
>
> The nature of the effort is to provide an easier to use 'Spring-like' API that can be used across various AMQP client libraries - just looking at Java and .NET ATM - and to provide some easy migration across versions of the spec.
>
> By 'Spring-like' this means that best practices regarding resource management (e.g. connections/channels) are handled for you and there is a POJO/POCO centric viewpoint to the API.  If you have seen Spring's JMS support, it is in the same style.   There is additional management code that goes above and beyond what is in Spring JMS as Alexis mentioned below.  The API to do this is 'custom', it is not based on the JMS spec.  There is also a programming model one can use that is part of the Spring Integration project.  There is also a .NET version of Spring Integration planned but no dates yet.
>
> As for versions of the .NET framework, we have not yet added anything specific to .NET 3.0/3.5/4.0 in the .NET code base.  You can still use the library from .NET 3.0/3.5/4.0 though.
>
> I think you will find the foundations of point #3 to be covered with the current work.  There is a JSON converter implemented (in both Java and .NET) and we've envisioned extending this out to other favorite serialization formats, protobuf, avro, etc.
>
> Last value cache can be a slippery slope with requirements.  I used work at Tibco (TFTI) and then Reuters.  Products like the 'TIC' from them start off simple and soon end up with a very complicated feature set.
>
> Would be good to discuss the Rabbit/Gemfire integration more.
>
> We are working on reflection based serializers for Gemfire ATM from the pure Gemfire developer productivity perspective.
>
> Generally speaking supporting language interop is very important part of this work with Rabbit/Gemfire.
>
> We should discuss in more detail the specific use cases you have.
>
> Mark
>
> https://src.springsource.org/svn/se-amqp
> https://src.springsource.org/svn/se-amqp-net
>
>
>> -----Original Message-----
>> From: alexis.richardson at gmail.com [mailto:alexis.richardson at gmail.com]
>> On Behalf Of Alexis Richardson
>> Sent: Monday, June 21, 2010 10:55 AM
>> To: John Apps; rabbitmq-discuss at lists.rabbitmq.com
>> Cc: jim at rabbitmq.com; Mark Pollack
>> Subject: Re: [rabbitmq-discuss] Rabbit crash, new persister
>>
>> John
>>
>> We commercially support RabbitMQ on Windows and provide support for
>> 100% free packages through this list.  RabbitMQ has a large number of
>> deployments on Windows and .NET.  People can rely on us to care about
>> this.
>>
>> RabbitMQ was the first AMQP implementation to support the CLR and WCF,
>> back in Feb 2008.  It was the first to provide an AMQP broker as a
>> Windows service.  This codebase has been actively improved
>> continuously since then.  However, since not every version of Windows
>> behaves the same way, there's no doubt more quirks to be hunted down
>> and dealt with or accommodated.
>>
>> RabbitMQ is also being integrated with Spring.NET thereby offering
>> customers TWO production frameworks for Windows based applications.
>> Although it has not been released yet, we have also integrated
>> rabbitmqctl into Windows management - effectively porting the
>> Alice/Wonderland model to a 100% Windows metaphor.
>>
>> In the cloud, independence from the underlying hardware does not free
>> you from the limitations of the O/S.  So we expect to continue to
>> support Windows and .NET in the cloud.  Please do however note that
>> Azure is a PaaS, offering a different runtime from vanilla .NET.
>>
>> Best wishes
>>
>> alexis
>>
>>
>>
>>
>>
>> On Mon, Jun 21, 2010 at 12:38 PM, Matthew Sackman
>> <matthew at rabbitmq.com> wrote:
>> > On Mon, Jun 21, 2010 at 01:15:01PM +0200, John Apps wrote:
>> >> I have suggested before that you place an official statement saying
>> that
>> >> Linux is the platform of choice; Windows is tolerated, or words to
>> that
>> >> effect. If you prefer to have everyone use Linux, then say so!
>> >
>> > Well that's not really the case. Windows is more than tolerated, and
>> we
>> > actually make more effort to support Windows than we make to support
>> OS
>> > X. It is the case that Linux is the platform of choice, especially
>> for
>> > a server, but we do not wish to dissuade people from using Rabbit
>> under
>> > other OSes. If there are things we are not doing which we should be
>> > doing to support any OS better, then we want to hear about it, not to
>> > put up some banner saying that we're uninterested.
>> >
>> >> I find it hard to take a product seriously when doubts are
>> constantly raised
>> >> about the platform I am running it on; makes me wonder if I am using
>> the
>> >> wrong product as I have no choice with the platform.
>> >
>> > I am genuinely curious - are we the only makers of software that you
>> use
>> > that you feel constantly doubt the platform you're running on?
>> >
>> >> *>>>*I'm yet to hear of anyone talking about Windows in the
>> >> cloud*(presumably because if you added a window to a cloud, you'd
>> let
>> >> the rain out).*
>> >> You may consider the above statement as in the category "devious" or
>> >> "dubious" - not helpful at all and blatantly incorrect. Amazon
>> offers
>> >> Windows in the cloud, MS offers it under the Azure label, MS
>> Business Online
>> >> Productivity Services is making inroads into Google Applications. To
>> name
>> >> but a few.
>> >
>> > That's very true, sorry for that.
>> >
>> > Matthew
>> > _______________________________________________
>> > rabbitmq-discuss mailing list
>> > rabbitmq-discuss at lists.rabbitmq.com
>> > http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> >
>