Brian, Thanks for your reply. >Since you mention services (plural) I assume some at least of these will be public ones over which you have no control.
This is n't true. The web services are going to be developed by an outsourcer only for us so I can modify the exchanged data types if necessary. My main question is if you have a VFP9 compatible WebService does worth the effort to base your new development in an unsupported technology like SOAP ? and if so, will you have problems deploying your app in Windows XP and Vista? Stephen, thank you too. >Did the WS team consider java consumption or only vs200? The WS are not yet implemented but now you brought another option in this trilemma : WCF! >WCF is a WS on a much more secure layer I can believe it, but this means that you have to build your EXE using .net framework 3.+ and deploy .NET framework 3.+ dependencies, dependencies dependencies ... Vassilis Aggelakos ----- Original Message ----- From: "Stephen Russell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 30, 2008 3:42 PM Subject: Re: Need your advice on Web services > On Jan 30, 2008 6:24 AM, Vassilis Aggelakos <[EMAIL PROTECTED]> wrote: > >> Hi Folks, I need your advice. >> >> I have a VFP app which - if client wants - uses MS SQL Server 2005 or MS >> SQL >> Server 2005 Express or MYSQL ( recommended if it is already installed but >> not deployed by me aka license issues ). >> >> Now wanting to extend the program features I am considering to make my >> app >> consume some web services that are written in C#. >> >> Do you believe that it is better to make my VFP app consume (and deploy) >> SOAP Web services or it is better to make an external EXE in C# to >> consume >> the web services? - (and then send the returned data back to my VFP main >> program?) >> >> I have read many many posts with different deploying problems of SOAP. Is >> it >> true? >> Do you believe that it is safe to assume that my 500+ clients will >> install >> SOAP files without problems? ( mainly WinXP , several Win 2000) >> >> Keep in mind that when my client selects MS SQL Server as a database, the >> .NET framework is installed anyway so the external EXE doesn't add any >> more >> headaches to be deployed - You have already overcome the troubles, if you >> manage to install MS SQL Server! -;) >> >> Any help would be greatly appreciated. > > ------------------------------------------------------------------------------------------ > > Your troubles could be few or major, depending on how the WS was designed. > Did the WS team consider java consumption or only vs200? > > Important point for newer WS implementations is are the calls being done > with a WCF methodology. WCF is a WS on a much more secure layer. A layer > that can be manipulated by the network admins and not need any programmer > to > fix a change that the network has to accomplish. Many will freak on these > words but this is going to really be harder for VFP in the future. > > So I would create the wrapper in .NET today either in house or contract it > out. > > If you do it in house you may find that .NET is pretty scary or pretty > cool. If they did their versionin C# and you liked VB better, no problem. > If you wanted you could do it in IronPython, still no problem. > > You could also write the wrapper in java. There are plenty of options. > It > just gives you one more layer that you have to maintain and support. > > -- > Stephen Russell > Sr. Production Systems Programmer > Mimeo.com > Memphis TN > > 901.246-0159 > > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
