Re: [Mono-dev] Fwd: [PATCH] System.Messaging using AMQP (RabbitMQ)
Hi Michael,
Michael Barker wrote:
Hi,
I have updated the bug report
(https://bugzilla.novell.com/show_bug.cgi?id=432471) to include a
first cut of MessageEnumerators. It does seem to work, originally I
though that an AMQP Ack would acknowledge all messages up to that
point, but that does not seem to be the case, so I can implement the
System.Messaging behaviour reasonably well.
Looks like (at least) Mono.Messaging.RabbitMQ/MessageFactory.cs is
missing. Can you please check missing stuff in the patch (probably
new files) ?
Well, I'm rather afraid of having Mono.Messaging base API dependent
on Rabbit (by dependent I don't mean that Mono.Messaging.dll has
reference to Mono.Messaging.RabbitMQ.dll). AMQP solution might not
be chosen if it lacks significant functionality, but that does not
mean it is no-go. If Rabbit based implementation does not work here,
I rather assume nothing would work fine here ;)
I would be useful if you could describe what you mean by dependent?
I'm assuming that you're referring to the design of the API. I've
tried hard to avoid designing Mono.Messaging based on the RabbitMQ
bindings. The majority of it is direct delegation from the
System.Messaging library (expect for the parts that don't need to
happen in Messaging implementation, e.g. formatting), so the
Mono.Messaging is more dependent on that library.
Sometimes we see System.Messaging bridge API, well, SPI, as to be
actually dependent (or premised) on the message queue implementation.
For example, if we return an array of Message (in bridge) to be used
in MessageEnumerator (sys.messaging), it may not be very efficient
for some queue systems that return IEnumerator of Message (it does
not have to iterate all messages just to create an array).
As long as the common SPI is direct delegation, it should be fine.
Also I think that Mono.Messaging should be considered only as an SPI,
not an API. Anyone writing an application requiring a brand new
OK (I didn't bother to differentiate API from SPI ;)
RE: AMQP, If its of any use here are a list of the main features and
how they can be supported:
Supported easily through the standard:
- Basic Messaging Send/Receive
- Message Listeners
- Transactions
Supported with a couple jumps through hoops:
- Peek() (may be better supported through queue browsers later on)
- Message Enumerators
Supported only with custom extensions to the server:
- {Receive,Peek}By{Id,CorrelationId,..}
Supported only with later potential protocol updates:
- Queue discovery
Thanks, that's a nice list of the features to be (or not to be)
supported :) For the time being, Peek and retrieval by IDs can
be left unimplemented. There would be a couple of ways to provide
queue discovery emulation through configuration, dummy management
queue or something else (apart from the queue system itself).
I think it'd be good way to create a branch for your implementation
in svn and let other people help hacking other implementations
(such as Win32API one, as I suggested earlier).
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Using Mono.Options in MS.NET
Hi, Now that Mono.Options is included in Mono 2.2 2.2? We've only just had the official release of 2.0! I've not seen anything on this list over a 2.2 release with tarballs or are you talking about svn? TTFN Paul -- Sie können mich aufreizen und wirklich heiß machen! signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Using Mono.Options in MS.NET
Yes, SVN Paul escribió: Hi, Now that Mono.Options is included in Mono 2.2 2.2? We've only just had the official release of 2.0! I've not seen anything on this list over a 2.2 release with tarballs or are you talking about svn? TTFN Paul ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] help needed please for ASP.NET migration to mono 2.0
Hi We use mono already for our server based software and its working well. With 2.0, we're starting migrating our ASP.NET application over as well. I'm using the VMWARE image for 2.0 Initially, I read the welcome to mono page on the VM and followed the copy you asp.net code to a folder under '/srv/www/htdocs' instructions and went to the local host URL and got a variety of errors (including one which was the giveway that firefox didn't know what to do with an aspx file) I then dug around and found the mojoportal site; backtracked into the /etc/apache2/conf.d folder, found the conf file and the 'webapp' config file under /etc/xsp/2.0/applications_available and copied them and modified to suite my application. If I access my default.aspx page now, I no longer get the errors and see the status bar at the bottom which says transferring data from local host which then changes to waiting for local host. Nothing furher happens. I've managed to set up the mono-control tool and that works but doesn't give me much additional information. The ASP.NET application is straight off VS 2005; it works fine under MS. It contains AJAX.NET. I've renamed Bin to bin. Given that nothing really happens, could it be something basic like its not compiling under mono on the first reference to the site? Help would be greatly appreciated. Regards Mike ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Marshaling DateTime type
Thanks everyone. I think my best bet will be to use the Tick property.
To: mono-devel-list@lists.ximian.com From: [EMAIL PROTECTED] Date: Wed, 15
Oct 2008 21:11:09 +0530 Subject: Re: [Mono-dev] Marshaling DateTime type
Hi, Robert Jordan [EMAIL PROTECTED] writes: Raja R Harinath wrote:
Robert Jordan [EMAIL PROTECTED] writes: FirstName LastName wrote:
What would be the best equivalent unmanaged type (linux and windows)
to use if I want to marshal a DateTime in the managed world (.NET,
mono)? You can't marshal DateTime directly because its internal
representation is different between runtimes *and* profiles. Use
DateTime.Tick (an int64) or a similar era-based representation.
But, IIRC, strangely enough, arrays of DateTimes should serialize fine.
So, you might be better of using a one-element DateTime array. Look at
DateTime's layout: public struct DateTime { private TimeSpan
ticks; #if NET_2_0 DateTimeKind kind; #endif } Nasty things
would happen if the unmanaged code is profile agnostic. From a quick
examination of the source code in SVN trunk, my understanding is that both
the Binary and Soap serializers have special cases for DateTime, which
aren't dependent on the exact layout -- and the serialization is
profile-dependent. (Of course, since I haven't actually tried it out, I
can't guarantee that it's fully interoperable with .NET.) - Hari
___ Mono-devel-list mailing
list Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
_
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] help needed please for ASP.NET migration to mono 2.0
disregarding the minor incompabilities, your application should run out of box on mono/linux. The only exceptions would be third party dlls using P/Invoke. Also you need to use Mono's System.Web.Extensions. Not microsofts. Other than that everything should work including ajax 2008/10/16 mike horsley [EMAIL PROTECTED]: Hi We use mono already for our server based software and its working well. With 2.0, we're starting migrating our ASP.NET application over as well. I'm using the VMWARE image for 2.0 Initially, I read the welcome to mono page on the VM and followed the copy you asp.net code to a folder under '/srv/www/htdocs' instructions and went to the local host URL and got a variety of errors (including one which was the giveway that firefox didn't know what to do with an aspx file) I then dug around and found the mojoportal site; backtracked into the /etc/apache2/conf.d folder, found the conf file and the 'webapp' config file under /etc/xsp/2.0/applications_available and copied them and modified to suite my application. If I access my default.aspx page now, I no longer get the errors and see the status bar at the bottom which says transferring data from local host which then changes to waiting for local host. Nothing furher happens. I've managed to set up the mono-control tool and that works but doesn't give me much additional information. The ASP.NET application is straight off VS 2005; it works fine under MS. It contains AJAX.NET. I've renamed Bin to bin. Given that nothing really happens, could it be something basic like its not compiling under mono on the first reference to the site? Help would be greatly appreciated. Regards Mike ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] help needed please for ASP.NET migration to mono 2.0
2008/10/16 mike horsley [EMAIL PROTECTED]: If I access my default.aspx page now, I no longer get the errors and see the status bar at the bottom which says transferring data from local host which then changes to waiting for local host. Nothing furher happens. I've managed to set up the mono-control tool and that works but doesn't give me much additional information. The ASP.NET application is straight off VS 2005; it works fine under MS. It contains AJAX.NET. I've renamed Bin to bin. Given that nothing really happens, could it be something basic like its not compiling under mono on the first reference to the site? If your app includes the MS System.Web.Extensions.dll in your bin folder, you should delete it because it can't run on Mono and will throw an error if you try to include it in the bin. Mono has its own copy in the GAC so deleting the one in the bin may help. If your app also depends on Microsoft.Web.Preview.dll, I'm not sure whether its supported, but again if its included in your bin folder it will prevent the app from running. probably there are errors you can review in the apache error log. You can get more info about what is happening with your app if you run it from the command line using xsp. Open a terminal cd into your web root folder and enter the command: MONO_OPTIONS=--debug xsp2 Now you can open a browser http://localhost:8080 to see run app and errors and or debug info will be shown in the terminal Hope it helps, Joe -- Joe Audette Software Solutions Architect Source Tree Solutions, LLC PO Box 621861 Charlotte, NC 28262 704.323.8225 [EMAIL PROTECTED] http://www.sourcetreesolutions.com http://www.mojoportal.com ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] problems compiling using System.Configuration using
Bill Using gmcs was the answer. Many thanks Mike Mike Horsley VQ Communications Ltd [EMAIL PROTECTED] T: 01249-460002 M:07920-151804 W:www.vqlive.com ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Using Mono.Options in MS.NET
2008/10/16 Paul [EMAIL PROTECTED]: Now that Mono.Options is included in Mono 2.2 2.2? We've only just had the official release of 2.0! I've not seen anything on this list over a 2.2 release with tarballs or are you talking about svn? Sorry, I was referring to this: http://tirania.org/blog/archive/2008/Oct-14.html Obviously there is no Mono 2.2 yet, but I was assuming from Miguel's post that it's as good as included in 2.2. Thanks, Avery ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Deploying on windows using mkbundle
Hi, I've ported my application to windows and now I'm trying to deploy it on this platfrom using mkbundle. My app runs with the executable generated by mkbundle but I need to set/hardcode an environmental variable (GST_PLUGIN_PATH=../lib/gstreamer-0.10), this way I don't have to call the executable from a .bat file. I think the best way is hardcoding it in the host.c file generated by mkbundle. I'm not used to program on windows and I don't witch is the default behaviour for this kind of problem. Thanks ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Deploying on windows using mkbundle
Hello, If you need that environment variable set for you process, you can set it at startup of you application. So, make one of the first things you do in your app: Environment.SetEnvironmentVariable(GST_PLUGIN_PATH, ../lib/gstreamer-0.10) This will be picked up by the current process, if I understand what you are trying to do. Thanks, Jonathan 2008/10/16 Andoni Morales [EMAIL PROTECTED] Hi, I've ported my application to windows and now I'm trying to deploy it on this platfrom using mkbundle. My app runs with the executable generated by mkbundle but I need to set/hardcode an environmental variable (GST_PLUGIN_PATH=../lib/gstreamer-0.10), this way I don't have to call the executable from a .bat file. I think the best way is hardcoding it in the host.c file generated by mkbundle. I'm not used to program on windows and I don't witch is the default behaviour for this kind of problem. Thanks ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Using Mono.Options in MS.NET
Now that Mono.Options is included in Mono 2.2, will it still be available separately? If not, it will be hard to build Windows-compatible programs that use it, unless people go digging throug the mono sources and extracting the libraries they like. I think it might be helpful to separate mono libraries that add functionality to any .Net application and mono libraries that implement the MS class library into two different projects. Am I missing something? You can always pull the code using the AnonSVN user interface from the web, it can produce tarballs of just the things that you need. Our todo list includes Make it easier to release components independently, would love to do it, we just need the spare cycles to make it happen in a general way for everything that we need. I think the tarball solution is pretty good, and we could just bundle solutions or files for the more complicated modules (Mono.Options is really easy to use). ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Using Mono.Options in MS.NET
On Thu, Oct 16, 2008 at 8:33 PM, Miguel de Icaza [EMAIL PROTECTED] wrote: Now that Mono.Options is included in Mono 2.2, will it still be available separately? If not, it will be hard to build Windows-compatible programs that use it, unless people go digging throug the mono sources and extracting the libraries they like. I think it might be helpful to separate mono libraries that add functionality to any .Net application and mono libraries that implement the MS class library into two different projects. Am I missing something? You can always pull the code using the AnonSVN user interface from the web, it can produce tarballs of just the things that you need. Our todo list includes Make it easier to release components independently, would love to do it, we just need the spare cycles to make it happen in a general way for everything that we need. I think the tarball solution is pretty good, and we could just bundle solutions or files for the more complicated modules (Mono.Options is really easy to use). Thanks, that answers my question. Avery ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
