Cart
[Home] [By Thread] [By Date] [Recent Entries]
Actually, making a COM-based Web Service interface to our current database is a button click operation today. Visual Foxpro supports it. Put the thing in the IIS directory and it works. It is the easiest bit Fox ever enabled. Remember, only a few have to implement SOAP et al. The rest of us are on the back of that. As one snail said to the other on the turtles' back , "Hang on! Here we go!" The question is, for how many users? If the interop specs don't work, it's just another balkanite on the Internet using a web client. len -----Original Message----- From: Paul Prescod [mailto:paul@p...] What's missing? Just you. You need to model your business process in terms of XML documents, hyperlinks between them and operations upon them. You can do that a) now, using HTTP, XML and URIs, or b) a year from now, using SOAP, some proprietary set of SOAP methods, XML bodies and some proprietary addressing scheme, or c) two years from now, using HTTP, XML and URIs. ;) Actually, I can't promise with 100% certainty that SOAP will go away...we could rebuild something HTTP-like on top of it, just for the thrill of reinvention.
|
