Ayende @ Rahien

Ayende Rahien commented on Raven MQ – Client API Design

Sat, 13 Nov 2010 22:39:57 GMT

Frank, If you have local tx, you can easily get distributed tx.

Frank Quednau commented on Raven MQ – Client API Design

Sat, 13 Nov 2010 15:47:08 GMT

These transactions then, you are just stating that a send is successful when you know it will be readable by other subscriptions, or are you getting into some distributed stuff?

Ayende Rahien commented on Raven MQ – Client API Design

Thu, 11 Nov 2010 20:56:31 GMT

Chris, Thanks, I'll probably apply both suggestions

Chris Patterson commented on Raven MQ – Client API Design

Thu, 11 Nov 2010 20:53:28 GMT

Gah, it stripped my Message tag from the second Handle method.

Chris Patterson commented on Raven MQ – Client API Design

Thu, 11 Nov 2010 20:51:59 GMT

Great to see some code snippets escaping, now on to some comments. You are using the concept of an endpoint, but since the queues are specified after the endpoint, aren't you really creating a connection or a channel to the queue service. A multiplex channel to RavenMQ seems to make sense from a naming perspective. On the subscribe semantics, could we combine the arguments into a pair of types, one for untyped and one for typed messages? My message handling methods could be: void Handle(RavenMQ.Message msg) { string body = Encoding.GetString(msg.Body); msg.Ack(); } Or for a typed message void Handle(RavenMQ.Message

Tom Dietrich commented on Raven MQ – Client API Design

Thu, 11 Nov 2010 15:21:53 GMT

To modify an old internet meme, "This Thread Is Useless Without Sourcecode!" Stop teasing me and let me under the hood already!

Scooletz commented on Raven MQ – Client API Design

Thu, 11 Nov 2010 14:49:03 GMT

As far as I see, you tend to close the whole message processing in an action to have it wrapped with a transaction. Am I getting it right? What about passed MEF container. Is is asked about all of the listeners/handlers of the specific message? If so, the DI in your handlers is saved!:D

Hoghweed commented on Raven MQ – Client API Design

Thu, 11 Nov 2010 14:28:58 GMT

Cool! I'm waiting to play with! I'm curious about the client api capabilities in a javascript environment, and I'm courios also to take a look to the code. Just one thing, I don't really feel comfortable with the message sending, because it seems a little bit ... difficult (sorry but words that cames in mi mind in italian could be translated just with "difficult")

Uturn commented on Raven MQ – Client API Design

Thu, 11 Nov 2010 14:19:28 GMT

where can I get this? really impress me about REST style interaction!!

json commented on Raven MQ – Client API Design

Thu, 11 Nov 2010 13:13:27 GMT

Looks tough.... ;)

J Healy commented on Raven MQ – Client API Design

Thu, 11 Nov 2010 13:08:53 GMT

Any IObservable features similar to ReactiveQueue? [http://rxcontrib.codeplex.com/](http://rxcontrib.codeplex.com/)