>>Anybody is doing Remote scripting? Any opinion on the subject?
>>TIA Mark
>
>Frankly I think this is a little gimmick, but not a heck of a lot more.
>
>I say this because in reality any Web application can already do this without requiring all the client component and proxy architecture. If you have a client side HTTP component (like XMLHTTP in IE) you can call an ASP page and get a result back - it's the same concept. THe way the remote scripting is implemented with proxy objects on the client and server and a Java applet - that's all overhead you can do without.
>
>The powerful concept is not hte scripting, but using the browser as a client to a server application, rather than having the server serving pages. IOW, your browser is running an application that calls on the server to get data and you're using the Internet as a network. I've been advocating this for years really.
>
>Why use straight Web requests and a standard like XML? Because it'll work from anywhere, not just a browser.
>
>For some more ideas on this check out:
>
>http://www.west-wind.com/wconnect/enterprise.htm
>
>there are a couple of examples how you can call VFP and COM methods on a backend server from the browser using only XML input and output. You can also run remote SQL queries in the same fashion. What's cool in this is that the same server codebase serves both a VFP client class and a pure IE browser running only the IE XML parser...

In this scenario Browser will process XML just like HTML to draw screens? Also what resources can I use to learn about what are saying in greater details?
Thans a lot Rick.
Mark