Applied to trunk, is this required in any of the previous branches?
Thanks for the patch.
Mike.
On Wed, Dec 16, 2009 at 11:00 PM, Jo Shields wrote:
>
> We had to remove RabbitMQ from Debian again, as the autogenerated-*.cs
> files were of unknown licensing (likely derived from non-Free spec
> f
> Sorry for not answering earlier. Environment variable would be perfect
> for me. Will this work sanely if multiple hosts are running the tests
> at the same time?
I've dropped in a commit which will pick up the hostname/port from the
MONO_TEST_RABBITMQ_SERVER environment variable. This will s
should also ensure that concurrent access to the
same box should not be an issue.
Mike.
On Mon, Sep 21, 2009 at 9:29 PM, Andrew Jorgensen wrote:
> On Fri, 2009-09-18 at 17:35 +0100, Michael Barker wrote:
>> > So the default installation is enough for the System.Messaging tests.
>>
> So the default installation is enough for the System.Messaging tests.
>
> At Novell we have multiple build machines running and it doesn't make sense
> to install
> RabbitMQ on all of them, so can we use a single remote instance for those
> tests? Will
> the test suite work if ran in parallel all
> Do you know of simple instructions on how to setup such server and
> configure it
> for the System.Messaging tests pass?
On Ubuntu you can add the apt repository and do a apt-get install.
Some instructions are here:
http://www.rabbitmq.com/debian.html#apt
The current implementation uses the d
> *test-System_Messaging-1.0:*
> Failures: 60 (too many to list here)
>
> Log:
> http://build.mono-project.com/WebServices/Download.aspx?workfile_id=529391
>
>
> *test-System_Messaging-2.0:*
> Failures: 60 (too many to list here)
>
> Log:
> http://build.mono-project.com/WebServices/Download.aspx?wo
> Is this info anywhere in the wiki? It would be nice if the
> System.Messaging page was updated... (and no, I'm not volunteering ;-).
Some updates made, I'll endeavour to keep it up to date as my work progresses.
http://mono-project.com/SystemMessaging
Mike.
l.com/), this is the best way to make sure Mono
has a decent Messaging implementation.
Regards,
Michael Barker.
On Tue, Jul 14, 2009 at 6:01 AM, Count László de
Almásy wrote:
> that's unfortunate. is there any viable alternative in Mono to
> System.Messaging?
>
> On Mon, Jul
Trunk is commited, I'll sort the 2.4 branch tomorrow.
Mike.
On Mon, May 25, 2009 at 7:22 PM, Miguel de Icaza wrote:
> Hello Michael,
>
> This looks great; Could you commit to both trunk and the mono-2-4
> branch?
>
> Miguel.
>
> On May 25, 2009, at 12:09 PM,
e QPid stuff and it appears that the python
client doesn't make use of generated code, but the Java, C++ and C#
version do, so I will check out their implementation too.
Regards,
Michael Barker.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
transactions work in AMQP vs MSMQ, the
transactional methods of MessageEnumerators can't be supported.
Regards,
Michael Barker.
Index: System.Messaging/System.Messaging/ChangeLog
===
--- System.Messaging/System.Messaging/Chan
leting the spec/*.xml files isn't a problem technically, but it
may mean that we do not have "all" of the source code.
Does Debian package Apache QPid or OpenAMQ? If so, how is it handled
those packages?
Regards,
Michael Barker.
On Sun, May 24, 2009 at 5:30 AM, Miguel de Icaza
Hi,
I've made a small amendment to the mono.1 page that mentions the
environment variable (patch attached).
Regards,
Michael Barker.
On Wed, May 20, 2009 at 7:45 PM, Gert Driesen wrote:
> Hi Michael,
>
> Can you also add a patch that documents the MONO_MESSAGING_PROVIDER
> env
No problem, split into 2 patches (compressed the rabbitmq upgrade as it is big).
Regards,
Michael Barker.
On Wed, May 20, 2009 at 6:40 PM, Atsushi Eno
wrote:
> Hello,
>
> It is not good for review. I'm ok with updating rabbitMQ itself,
> but it'd be better to rather
Hi,
The attached patch upgrades the RabbitMQ libraries to version 1.5.3
and includes a couple of fixes to the Mono.Messaging code as a result,
please review.
Regards,
Michael Barker.
rabbitmq-upgrage-1.5.3.patch.gz
Description: GNU Zip compressed data
Hi,
Small patch that adds some comments and allows dynamic initialisation
of MessagingProviders by specifying the MONO_MESSAGING_PROVIDER
environment variable.
Please review.
Regards,
Michael Barker.
Index: Mono.Messaging.RabbitMQ/Test/Mono.Messaging.RabbitMQ/ChangeLog
Hi,
My development work on System.Messaging is going to go on hold for
around 3 months, as I am about to head off back-packing around
South-east Asia. I will pick it back up again when I get back to the
UK.
There hasn't much progress over the last couple of weeks. I burned a
fair bit of time up
Hi,
The attached patch moves the message formatter tests to the
Mono.Messaging.RabbitMQ namespace and fixes some test failures.
Please review.
Regards,
Michael Barker.
Index: System.Messaging/Test/System.Messaging/BinaryMessageFormatterTest.cs
==
--- Mono.Messaging.RabbitMQ/Test/Mono.Messaging.RabbitMQ/ChangeLog (revision 122085)
+++ Mono.Messaging.RabbitMQ/Test/Mono.Messaging.RabbitMQ/ChangeLog (working copy)
@@ -1,3 +1,8 @@
+2009-01-03 Michael Barker
+
+ * AsyncPeekTest.cs: Added
On Sun, Dec 21, 2008 at 7:02 AM, Michael Barker wrote:
>> Thanks :) Though I have one request; they had better be made as virtual
>> in Mono.Messaging so that 1) those who derive from the driver do not
>> have to implement them by default, while 2) they can be implemented
&
.
Index: System.Messaging/System.Messaging/ChangeLog
===
--- System.Messaging/System.Messaging/ChangeLog (revision 121890)
+++ System.Messaging/System.Messaging/ChangeLog (working copy)
@@ -1,3 +1,8 @@
+2008-12-20 Michael Barker
> I think it would be ok to use an environment variable for both 1.0 and 2.0
> profiles.
I will aim to have the 2.0 profile support both an environment
variable and System.Configuration, probably with System.Configuration
taking preference.
___
Mono-deve
On Sun, Dec 14, 2008 at 12:05 AM, Michael Barker wrote:
>> System.Configuration.dll is only within 2.0, though I wouldn't care
>> much for dropping 1.x support. We could alternatively use environment
>> variable (we use it for registry and eventlogs for example).
>
>
> System.Configuration.dll is only within 2.0, though I wouldn't care
> much for dropping 1.x support. We could alternatively use environment
> variable (we use it for registry and eventlogs for example).
I would definitely prefer to drop 1.1 support. The 2.0 language
features, and not having to
> After a couple of struggle with build system, it's in trunk now :)
Cool I have it checked out now.
> I made a horrible hack in RabbitMQ/Makefile that now it includes every
> sources outside src/client as DISTFILES. There may be better way to
> reduce this kind of mess. Probably we can build thi
> Hello,
> This is looking great, thanks for the implementation :) I'll try and
> checkin the patch in the branch. I'm also thinking to move your code
> to trunk.
Cheers, that good news, it will motivate me to continue working on it :-).
___
Mono-devel-
Hi,
I have created a bugzilla entry
(https://bugzilla.novell.com/show_bug.cgi?id=457089) that contains 4
patches that add a chunk of functionality to the AMQP/System.Messaging
implementation. If possible, could someone commit them to the
messaging-2008 branch.
The patches add full support Peek,
d;
+ this.isDelivered = true;
}
}
}
Index: Mono.Messaging/Mono.Messaging/ChangeLog
===
--- Mono.Messaging/Mono.Messaging/ChangeLog (revision 116599)
+++ Mono.Messaging/Mono.Messaging/ChangeLog (working copy)
@@ -1,3 +1,11 @@
+2008-1
s to it I'll be happy to work from there.
Regards,
Michael Barker.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Forgot to CC the list.
-- Forwarded message --
From: Michael Barker <[EMAIL PROTECTED]>
Date: Sun, Oct 12, 2008 at 5:46 PM
Subject: Re: [Mono-dev] [PATCH] System.Messaging using AMQP (RabbitMQ)
To: Atsushi Eno <[EMAIL PROTECTED]>
Hi,
I have updated the bug r
P uses a declare
model, i.e. all queues exist, but its not possible to find what they're
called. Queue discovery is being considered for a future revision too.
Mike.
On Mon, Oct 6, 2008 at 9:08 PM, Michael Barker <[EMAIL PROTECTED]>wrote:
> Hi,
>
> Patch at
Hi,
Patch attached bugzilla report.
https://bugzilla.novell.com/show_bug.cgi?id=432471
Regards,
Michael Barker.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
fairly big
(2MB) and I had forgotten to add "Patch" to the subject line. I can
resubmit the email if required.
Regards,
Michael Barker.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Sorry accidentally sent without finishing the mail.
On Sun, Sep 28, 2008 at 10:42 PM, Michael Barker <[EMAIL PROTECTED]>wrote:
> Hi,
>
> Attached is 5 patches which make up an AMQP implementation of RabbitMQ.
> This is my second attempt, previously I used the qpid libraries, b
I've updated the code on googlecode to support MessageQueue.CreateQueue and
changed the license to LGPL 2.1.
Regards,
Michael Barker.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-
System.Messaging hasn't been
>> touched a few years, so a few more months shouldn't hurt :-).
>>
>> Oh. Okay. Though it has not been touched for years, I once tried to
> implement some basic functionality using OpenWire.net, and there was a
ember. I'll fix the license and add MessageQueue.Create support
before I go. I still want to help build a System.Messaging implemenation so
I would be happy to receive any feedback you have in order to build
something that will be useful for Mono. System.Messaging hasn't been
touched a fe
receiving with XML and Binary formatting works.
Regards,
Michael Barker.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
ed.
> - Original Message
> From: Atsushi Eno <[EMAIL PROTECTED]>
> To: Michael Barker <[EMAIL PROTECTED]>
> Cc: mono-devel-list@lists.ximian.com
> Sent: Thursday, April 10, 2008 4:49:25 AM
> Subject: Re: [Mono-dev] [PATCH] System.Messaging initial provider layer
mono-clean.
I have attached a patch that bundles the 2 to this email.
Regards,
Michael Barker.
Andreas Färber wrote:
Hi,
Am 02.04.2008 um 22:30 schrieb Michael Barker:
I am interested in working on an implementation of System.Messaging.
In that case it would be best if you used the Subversion
40 matches
Mail list logo
