asp.net - Self Tracking Entities vs POCO Entities -


we starting new web based product in planning expose our business logic through wcf services. using asp.net 4.0, c#, ef 4.0. in future want build iphone applications , wpf applications based on services. have been reading lot using poco vs self tracking entities (ste) , understand stes not work web scenario. can shed more light on issue?

for me ste absolutely wrong concept. implementation of dataset.

  • in asp.net application have store stes somewhere among requests. in first request query datasource ste , provide data in page. in next request (postback) want modify ste returned data browser. support tracking have use same ste in first request => have store ste in viewstate (if want use asp.net webforms) or session.
  • ste useless soa or interoperability. tracking logic part of ste = running on client. if expose ste in service immediatelly expecting client side use same tracking features included in ste logic. these features not provided other side automatically. in .net have them because share assembly stes. on other platform have explain developers how implement ste logic make work on side. limiting case because of iphone application.

Comments

Popular posts from this blog

unicode - Are email addresses allowed to contain non-alphanumeric characters? -

c++ - Convert big endian to little endian when reading from a binary file -

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -