Ron, I was having this discussion today, and wasn't able to express the distinction between the two models very well. I think you are right in calling one a client (JS) server (WCF style service). But what would you call the other model?
Thanks, Erick On Mon, Jan 24, 2011 at 7:53 AM, Ronald Woan <[email protected]> wrote: > This is the same discussion that Ruby developers seem to be having regarding > Rails vs Sinatra once you get past some point of complexity in clientside > Javascript applications. > I initiated similar discussions at the #alnetseattle meetings a couple years > back as I was struggling this migrating from XBAP/WPF applications to > heavyweight extjs (sencha) applications. At that time, I ended up with WCF > webservices as the backend as I don't even think routing added much value. > Over time we modified this to use JSON in many cases. > At some level I think we are just getting back to a client server model > interacting through a services abstraction. A related discussion on the > mailing lists has been what kind of model belongs on a client. > Ron > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
