Or is the same instance used for each (un)marshaling? It would be nice to have a cache and a duplicateMsgChecker function, from the app above to ensure transactional guarantees, and object ref substitutions during (de)serialization, to enable durable distributed objects and promises.
Subject: Re: could an Encoder/Decoder be stateful?
The encoder instance can't be shared in different producers since it's instantiated through java reflection. Decoder instance can actually be shared by different consumers since it's passed in directly through the consumer api.
Jun On Thu, May 16, 2013 at 5:58 AM, Withers, Robert <[EMAIL PROTECTED]>wrote:
Subject: RE: could an Encoder/Decoder be stateful?
Thanks, I created KAFKA-909 for the feature request.
As an aside, I see that in Jira, the available kafka versions are 0.8, 0.8.1 and 0.9. I see the branch in github for 0.8, does this mean that the trunk is 0.8.1? And 9 is future planning on jira, but not established in github, yet?
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext