I put that limit in, and made it hard enough to bypass for a reason. Have you considered the implications of this? Usually when you have collections of ids, it means a query per id, and when you have that many queries, it is VERY expansive. It also opens up for a message with thousands and tens of thousands (or more) items. Unbounded result sets are a very problematic (and common) thing.
I understand the requirement as set, but what about the other stuff that is involved? On Fri, Jun 17, 2011 at 11:33 PM, René M. A <[email protected]>wrote: > Yes, the message contain commands which must be executed against a number > (potentially many) of hardware units on a low bandwith network. The ids of > the requested hardware units is also part of the message. the service > receiving the message knows the network and how to efficiently execute the > commands in the network based on the list of hardware unit ids. > > So to make it short, the list must be kept together. I know I can split the > message and use saga's to combine it again or implement a serializer > extension, just thought it was bit much work to do simply to transfer a list > of ids. > > Glad we had the discussion though. Thanks for the input. > > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rhino-tools-dev/-/NAVpW8C_xcYJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
