H
hazz
if I think about efficiently sending data back and forth through a
webservice for a 'typical' application (in this case smart client using
Composite UI application block) what questions do I ask that would point me
toward the optimum mechanism(s) using XML as the payload vs. serialized
hydrated objects vs. hybrid vs. ?? . If I think about the webservice like
the eye of a needle and I am pulling thread (data) through that eye back and
forth, like flossing teeth, I want small and fast. The business and database
layers need to efficiently pack it up and the client side to unpack it. Visa
versa for updates/inserts. I will be using SQL Server 2005 and .net 2.0.
thanks for helping me ask better questions and thinking about this the right
way.
-hazz
webservice for a 'typical' application (in this case smart client using
Composite UI application block) what questions do I ask that would point me
toward the optimum mechanism(s) using XML as the payload vs. serialized
hydrated objects vs. hybrid vs. ?? . If I think about the webservice like
the eye of a needle and I am pulling thread (data) through that eye back and
forth, like flossing teeth, I want small and fast. The business and database
layers need to efficiently pack it up and the client side to unpack it. Visa
versa for updates/inserts. I will be using SQL Server 2005 and .net 2.0.
thanks for helping me ask better questions and thinking about this the right
way.
-hazz