On 10 Apr 2013, at 20:57, Sanne Grinovero <[email protected]> wrote:
> Right, let's keep this to collecting requirements: +1. Ok, so it seems we're all pretty much in agreement that metadata extraction and indexing should happen on the server side and not on the client. As I said before, this is good. Simple clients, support for re-indexing, support for changes in indexing characteristics, and the ability to save the world from AIDS. This puts a requirement on an efficient and portable serialisation format. Again, +1 to starting with defining what we need. Good start below, Sanne. > - being able to upgrade the server without losing data > - being able to change the (soft) schema on the server > - read/write fields from different languages > - deal with multi-version control of values (i.e. being able to read > an older value through an evoluted schema, doing comparisons of same > value even if it was stored using different schema generations) I'd add: * Support for fast and easy translation to/from object model in high level language of choice (i.e., not manual parsing! Maybe some form of tooling, like a Maven plugin, to generate "IDL"-esque format) * Serialisation efficiency (size and speed) should be considered And in addition, I'd also list out existing technologies that fulfil some or all of these requirements that we can consider, look at extending, etc. - Manik -- Manik Surtani [email protected] twitter.com/maniksurtani Platform Architect, JBoss Data Grid http://red.ht/data-grid _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
