2011/11/19 Raffaele P. Guidi <[email protected]>: > We could also provide a high performance serializer/deserializer based on > protostuff... but, in any case let's follow the simplest path to > demonstrate the case, there will always be room for improvement. I'm sure > Mir will show us something as soon as it will be ready... I used to put > stuff in github gists, in these cases, what is the best way for the ASF?
patch in a jira entry. > > Ciao, > R > > On Sat, Nov 19, 2011 at 5:59 PM, Thomas Vandahl <[email protected]> wrote: > >> On 19.11.11 09:43, Raffaele P. Guidi wrote: >> > It depends on what JCS requires to manage. If it handles tcehe key-valu >> > mapping on its own (as I suppose it does) you shouldn't need to use DM's >> > CacheService (it would be a waste of memory) which does the same. >> > CacheService puts KV mapping on top of MemoryStorageService (and some >> more >> > things such as the background jobs for eviction that maybe are already >> > handled by JCS) . >> >> Yes that is the case. JCS auxiliaries are just an extension to an >> existing cache infrastructure. JCS handles everything from key-value >> mapping to event handling, idle time and life time management. For >> auxiliaries, there is a pluggable serializer/deserializer available. >> >> If possible, I would like to see some code to get a better idea of what >> your plans are. >> >> Bye, Thomas. >> >> PS: I'm subscribed to [email protected], so we can drop the >> personal mail addresses from the communication. >> > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
