Aaron,

It seems to me that the "rich client" model is VERY successful in the real
world. In the past, we had RealPlayer. Flash is one that is common right
now. And, the best example of a thick client that reeks is Apples iTunes.
This is extremely successful.

And, if you want to debate the thick client problem, isn't a browser a thick
client, technically? And aren't we often just working around the various
limitations of the browser client? Wouldn't the preference be to have your
OWN thick client, deployed better (more like Flash than iTunes), and get rid
of all the issues of client discrepancies?

Seems to me a GOOD thick client fits right in to your model??

Trevor



On 7/17/08 10:34 AM, "Aaron Bartell" <aaronbartell@xxxxxxxxx> wrote:

Putting the Controller on the client reeks
of thick client deployment issues, because you know that the Model will also
seep into there and the size of updates to download before you can run the
app will become much more than what shops desire.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.