Why not just put the order lines in the same message as the order? I mean, ultimately you're just adding a dictionary where the keys are the product ID and the values are the quantities. You'd need many thousands to get anywhere near any limit of MSMQ.
-- Udi Dahan From: rhino-tools-dev@googlegroups.com [mailto:rhino-tools-...@googlegroups.com] On Behalf Of Ayende Rahien Sent: Thursday, October 14, 2010 9:33 AM To: rhino-tools-dev@googlegroups.com Subject: Re: [rhino-tools-dev] Rhino ESB - 256 Item Collection Limit. Jared, The reason that this limit exists is to serve as an early warning system. If you can have more than 256 items, you might have a lot more. And if you have that, you might hit the physical limits of message sizes. So yes, the recommendation is to break the message to multiple messages, which would mean that you can now handle orders of unlimited size. If you really want, however, you can replace the serializer with one that doesn't have this limit On Thu, Oct 14, 2010 at 5:21 AM, Jared Kells <jke...@gmail.com> wrote: Hi All, I have just run into the 256 item limit for collections in a service bus message. I understand from Ayende's blog that this is a design decision to actively fight against me doing something I shouldn't but I don't know why I shouldn't! Take for example the action of adding a new sales order. I send a batch to the server containing all the messages required to add an order. One of those message contains a collection of line items. I process the batch on the server in one NHibernate session / transaction. This action of adding an order is an atomic operation, the order makes no sense with only half the lines. The problem is that orders regularly contain more then 256 lines. How should I be sending a new order over the bus? It seems like a lot of work to try to split them up, store them somewhere temporarily and then write them to the database when I have them all. Maybe I'm just approaching this totally wrong? Kind Regards Jared Kells -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to rhino-tools-...@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com <mailto:rhino-tools-dev%2bunsubscr...@googlegroups.com> . For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to rhino-tools-...@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en. No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.862 / Virus Database: 271.1.1/3194 - Release Date: 10/13/10 08:34:00 -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to rhino-tools-...@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
