Another option to potentially look at is using Fast-Infoset. I don't know if JBoss supports it, and it's not supported outside of Java, but it's goal is to seriously reduce the serialization and de-serialization using a near binary representation.
A web service is exposed with both the Fast-Infoset and a normal non-binary one.. The selection can be made in the http hearders. So a .Net client could invoke the web service with the non Fast-Infoset version and other java clients could invoke the Fast-Infoset model. Microsoft is working on something similar in the upcoming Communication's Foundation (Indigo), so it sounds like there will be some time before it's agreed upon by all parties. In the end though, it sounds like it's going to happen in some form. This tied in with MTOM, will go along way to reduce the over-head and size of the data. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921893#3921893 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921893 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
