-
1. Re: London Meeting (Feb 2006)
ovidiu.feodorov Feb 16, 2006 9:16 AM (in response to ovidiu.feodorov)Meeting documented in the same wiki entry (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingDesignMeeting20060206_10)
Meeting notes collected in:
http://jira.jboss.org/jira/browse/JBMESSAGING-134
http://jira.jboss.org/jira/browse/JBMESSAGING-231
http://jira.jboss.org/jira/browse/JBMESSAGING-232
http://jira.jboss.org/jira/browse/JBMESSAGING-234
http://jira.jboss.org/jira/browse/JBMESSAGING-236 -
2. Re: London Meeting (Feb 2006)
ovidiu.feodorov Feb 16, 2006 9:21 AM (in response to ovidiu.feodorov)Other conclusions/ideas (no JIRA tasks for them yet)
Bug in ordering
===============
Currently message ordering is created on producer - we need to do this on server
e.g. producer1, producer2
producer1 sends message a with order number 1000000
producer2 sends message b with order number 1
producer1 sends message c with order number 1000001
producer2 sends message d with order number 2
then after ordering is applied in db, the messages are received in order b, d, a, c i.e. starvation occurs
the message ordering should be provided by the channel - the channel should keep a counter
Compression
================
The payload byte[] can also be compressed (gzip) and passed around as compressed data
xpath
================
Use xpath to implement selectors