Bonnie;

I agree and in fact it seems like terms used to describe software development change from time to time. Remember when Microsoft used the term, “Screen”, and then it became “Form”? Consume – it sounds like a disease!

consumed (engulfed by flames)

instantiated (born before your eyes)

threads (clothing)

garbage collector (sanitary engineer)

security (a tragic comedy in progress)

temporary resources (credit cards)

windows service (Windex)

browser experience (no comment-please read my mind and excuse the use of old English terms)

Common dialogs (the vernacular)

Web services (or the lack there of)

Extensible (?)

Persist (do not give up)



Tom



>You're welcome Dmitry. I think you get it now.
>
>I have always thought the phrase "consume the Web Service" was a little silly. Basically you're just calling a method on a Web Service, I have no clue why anyone decided it should be known as "consuming".
>
>~~Bonnie
>
>
>
>
>>Bonnie,
>>
>>Yes, this is how I understand it. I think I probably didn't express myself correctly in my initial message: I thought that when a client (be it VFP or .NET app) consumes (calls) the Web Service it (client) also runs Web Service. Now I understand that this is not technically correct.
>>
>>Thank you.
>>
>>>Dmitry,
>>>
>>>Yes, the Web Service would need to be on the Web Server. Yes, the VFP client app would need to consume the Web Service. You can have your VFP client app call the Web Service when the app first starts up and, if you need to, periodically call the Web Service (maybe with a timer) while the client app is running.
>>>
>>>~~Bonnie
>>>
>>>
>>>
>>>>>>I am playing with the following idea and would like to hear opinions of people who have done Web Services and what they think about it.
>>>>>>
>>>>>>I have a customer that wants to have a web-based order system. But they don't have a web server (their are relatively small company).
>>>>>>What I am thinking is the following:
>>>>>>1. Create a web-based order application on my site, that is on my web server (I actually don't have my own but renting one). This application will store the orders in either VFP database or SQL Server database on the Web server.
>>>>>>
>>>>>>2. I will have a Web Service application residing on a user PC that would have a timer and periodically the Web Service would "get" the orders from the VFP or SQL Server on the web server. Then the Web Service application would add these orders to the desktop windows (VFP) application.
>>>>>>
>>>>>>What do you think?
>>>>>>
>>>>>>Thank you in advance for any input or suggestions.
>>>>>
>>>>>I think you have it backwards, Dmitry. A better solution is to create a web service that outputs all of the "new" orders. Run the web service on your rented web box. Then the VFP client app checks for new orders periodically.
>>>>>
>>>>
>>>>But how would VFP client check for new orders? It (VFP client) has to make a "call" to the Web Service on the web box, correct? And if I am correct their, the VFP client has to use consuming Web Service.
>>>>
>>>>Do I understand the concept correctly?