On Sun, Aug 16, 2009 at 11:28 PM, philippe van dyck<[email protected]> wrote: > Sure, but my current implementation includes caching in an expiring map, a > connection pool, and each operation on a specific reference is queued and > added in a 'producer' blocking queue emptied by a couple of consumer > threads...
Sounds more like a production-grade one. I suggest that you commit it straight into qi4j-extensions. To receive commit rights to platform, send me a SSH public key in accordance to http://www.qi4j.org/codebase.html > Although, each aspect is isolated in a different class/package, do you want > me to produce a simpler one, more like the one available right now ? I think not, and instead we can look at the possibility to break out some of that functionality for generic re-use together and over time. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
