Just one other point.... I submit that even you, with the last sentence in your reply, has a bias toward SPT....

So, I guess that makes you one of the "some folks" too...< bg >...

On one hand, you say it is not a black and white issue. You then conclude by making it a black and white issue. If SPT is what you would consider for a non-trivial app, would you really take the time to defeat that decision if based on experience, SPT was the way to go?

You say you only use SPT these days? And yet, you then couch that by saying that it is due to the project's requirements. And finally, you couch that by stating that you are not giving into dogma.

You eschew dogma, yet, you cite the - (your) - wiki as a doctrine that provides a roadmap of decision making in this matter. In short, your stance is inconsistient.

The fact is Steve, you use SPT because it is technically superior to RV's. If it were not so, you would not use SPT.

Next time, if you want to take a cheap shot, you better bring more to the party!




>I don't think you've received good advice so far. It's not a black and white issue, and moreover some folks have vested interests and well-known biases on this topic.
>
>Here are two good wiki pages that summarize the forces that tip any decisions, one way or another, depending on your circumstances.
>
> http://fox.wikis.com/wc.dll?Wiki~RemoteViews
> http://fox.wikis.com/wc.dll?Wiki~MoreOnRemoteViews
>
>FWIW I'm using only SPT these days, but that's due to the project's requirements, not a particular dogma. SPT is definitely the first thing I'd consider for non-trivial applications.
>