For JMS I also would use a message property. That's what they are for. --Hardy
On Fri, 22 Jul 2011 14:11:48 +0200, Sanne Grinovero <sa...@hibernate.org> wrote: > Hello all, > With HSEARCH-761 each index can be configured with a separate backend; > one possible configuration is a "multi-master" in which LuceneWork > operations related to different indexes are sent to different > backends, possibly on different cluster nodes but not necessarily. > > So while before the "target index" was part of the message as it could > be inferred from the operations and involved indexed classes, now it's > a metadata attached to the message as a receiving backend could assume > that all operations it receives need to be applied and the only index > it's managing, but I still want to transmit it so that a single > backend will still optionally be able to handle multiple indexes, as > it did before. > > Different backends are mapped by the index name, eventually with a > shard postfix, so I need to label the messages with a String for the > receiver to know how to deal with them. > Shall I attach this as a JMS "stringProperty", or shall I encode it as > part of the payload? > I think it should be a property so that people can deal with it in > flexible "JMS ways", but I'm not sure. Both strategies are easy to > implement. > > Regards, > Sanne > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
