We are adopting a serialization framework (Google's Protobuf) in order to properly support backward compatibility with binary serialized sessions. Our existing serialization framework was/is good for when we implement session replication/HA, but was very complicated for long term, disk persistency and backward compatibility.
We will now have a documented serialization format, as well as the possibility of partial serialization for jBPM, and security features like signing sessions with public/private keys to prevent attacks in a non-safe environment. Edson On Mon, Mar 19, 2012 at 1:15 PM, Esteban Aliverti < esteban.alive...@gmail.com> wrote: > Just for curiosity, what is the new serialization protocol? > > Best Regards, > > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX > > Esteban Aliverti > - Developer @ http://www.plugtree.com > - Blog @ http://ilesteban.wordpress.com > > > On Mon, Mar 19, 2012 at 6:13 PM, Edson Tirelli <ed.tire...@gmail.com>wrote: > >> >> All, I am about to do a big commit into the master branch (as in >> roughly 98 changed files with 35,731 additions and 1,795 deletions. ). >> This is the implementation for the new serialization protocol. I will do >> that in 1 hour from now... if anyone needs me to wait, please speak now or >> never... :) >> >> Thanks, >> Edson >> >> -- >> Edson Tirelli >> JBoss Drools Core Development >> JBoss by Red Hat @ www.jboss.com >> >> _______________________________________________ >> rules-dev mailing list >> rules-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/rules-dev >> >> > > _______________________________________________ > rules-dev mailing list > rules-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-dev > > -- Edson Tirelli JBoss Drools Core Development JBoss by Red Hat @ www.jboss.com
_______________________________________________ rules-dev mailing list rules-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev
