Le 16/07/2013 12:02, Aristedes Maniatis a écrit : > I started trying to read through the diff as a whole, but maybe I need to > break it down into before and after the big whitespace change [1]. I tried > reading the commits separately, but many of them don't make any sense to me. > What does this commit [2] have to do with memcache?
You'd better walk the revision history commit by commit. Hessian is developed along Resin, so the commit messages are often not directly related to Hessian. IMHO Hessian is so useful that it could deserve its own sub project with an independent release cycle. It has the potential to be supported by a wide community of developers. > I see Java 4 has been left behind with generics now in the code. And bunch of > new serialisers for either better performance or reliability when dealing > with particular fields. I also see some changes to the way compression is > handled (although not sure how that interacts with servlets and our > experiments aren't conclusive). Hessian clients now handle compressed responses (when the "Content-Encoding: deflate" HTTP header is present). This is part of a patch I submitted some time ago. It's still missing compressed requests and compression support in HessianServlet. > There are quite a few changes to the code. Emmanuel, would you be able to > give us the 50 word or less version of the major changes we should be on the > look out for? I think you already summarized it pretty well. Hessian 4.0.33 is faster, more reliable and more capable than Hessian 3.1.6. Emmanuel Bourg _______________________________________________ hessian-interest mailing list hessian-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/hessian-interest
