>
I think the most important considerations for Web Services should be performance and stability. It's too early yet to tell what the story will be there. Since Web Services are accessed through a URL via SOAP protocols, which can be running on any system anywhere, there's less glue necessary to tie them in. In fact, ASP+ won't even be necessary for serving them up.
>

I agree that VFP can play in this space. However, playing in that space and being the most efficient are two different things. Do you think for one moment the architects involved are going to allow the scenario of VFP performing better or being more stable than web services built in VB or C... I don't think so...


>
I don't think we're speaking the same language here, John. Based on how I picture it, 99% of Web Services is gonna be all about data. Where the data resides, and how it's massaged and served up into SOAP and XML responses, are issues of physical implementation, and it's at that decision point that VFP's data engine will be a major factor.
>

Let me put it this way..if VFP's data engine where that strategic and that much better, it would find its way into .Net. .Net has a pretty good data engine. It's called SQL Server..< vvbg >... Again, my comments related to VFP's data engine being irrelevant. It was a very specific statement..


>
VFP-based Web Service solutions will be easy to create and maintain, and will absolutely scream due to the local data engine.
>

Here are two of your sentences from above:

"I think the most important considerations for Web Services should be performance and stability. It's too early yet to tell what the story will be there."

That said, how do you know VFP-based web services will be easy to create and maintain. And, how do you know they will "scream" due to the local data engine? You couch this conclusion from the standpoint that the other tools will be less easy to maintain? That they will not scream?

This local data engine advantage that VFP supposedly has, I just don't see it. I cannot reconcile the fact that if it were that good, you would see it perpetuated. My feeling is that best parts of it have been absorbed by other tools.

sorry, I just don't see it..... single tier/two-tier C/S apps, VFP is the way to go. Web based/multi-tier apps, there are better tools suited to the task.

Come Devcon time, for those of you that go, you will see something from a vendor that is absolutely going to knock your socks off. Up to that time, you would have bet the ranch and the dog that "it" could not be done.

I am not going to spill the beans on what "it" is just yet. I will tell you what "it" is not. It is not Fox. And one part of what "it" is - DATA