Assaf Arkin wrote: > On the contrary. You pay CPU time trying to serialize a complex object, > regardless of your bandwidth. The more complex the graph the slower > serialization will be, the more large the the objects are, the more > bandwidth would help. So, passing around a huge String would benefit > from a fat pipe. Passing around a complex heirarchy of small objects > would benefit from a better CPU. > > > The current project I'm on uses JSP pages and servlets to generate the > > user interface, so my "client" is in the same datacenter as my "server", > > and they are connected over a high speed network. Why can't my servlets > > and JSPs manipulate the same complex graphs of fine-grained domain > > objects that my EJBs manage? All of my serialization and deserialization is happening on big honkin' multi-processor boxes in a gleaming datacenter. I have no shortage of CPU cycles or network bandwidth. I understand your point, I just don't think that it implies that PBV objects should always be atomic. What I am short of, on the other hand, are developer hours. Allowing my team to work with complex object graphs increases their productivity manyfold.
begin:vcard n:Wilson;Chip tel;fax:(214) 358-0353 tel;work:(214) 642-4559 x-mozilla-html:TRUE url:http://www.axyssolutions.com/ org:Axys Solutions adr:;;;Dallas;TX;; version:2.1 email;internet:[EMAIL PROTECTED] title:Application Architect note:Sun Certified Java Architect x-mozilla-cpt:;-25088 fn:Chip Wilson end:vcard
