Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > .NET > Other .NET > .NET Web Services
Password Reminder
Register
Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
.NET Web Services Discussions about .NET XML Web Service technologies including ASMX files, WSDL and SOAP.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the .NET Web Services section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developersí questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Display Modes
  #1 (permalink)  
Old July 7th, 2004, 08:35 PM
Registered User
 
Join Date: Jul 2004
Location: , , .
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default usabiity of web services

hi ppl,
im facing a design problem im hoping some experts here on the forum can help me out with.
i have some experience with webservices but cant make up my mind on this one.

my company is in the design stage of building a new appointment scheduling product. later on this will be part of a larger suite of products. currently, for just the scheduling part of the application, someone in the team came up with the idea of making all the server end web services based.

the target deployment would be an intranet lan with one server and multiple clients connections using a client program (not via the web/browser) the fat client would use the web methods to retrieve all the required data from the database such as patient information, appointment availability etc. thus we would have quite a lot of web methods serving up this information to multiple clients.

the reason my team-members are in favour of this architecture is because security and firewall problems are a non-issue because of the very nature of web services. they say that using authentication, they can lock down the clients connecting to the server end

the reason i do not like the idea of having all the web methods is because anyone can point wsdl to the server and build a client. also, the way i understand web methods is that they are well suited for public information (example: a stock quote), but in this case the data is VERY private and any breach could lead to major legal issues.

please advise,
thanx in advance
Reply With Quote
  #2 (permalink)  
Old July 8th, 2004, 08:53 AM
Friend of Wrox
Points: 3,489, Level: 24
Points: 3,489, Level: 24 Points: 3,489, Level: 24 Points: 3,489, Level: 24
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Central, NJ, USA.
Posts: 1,102
Thanks: 0
Thanked 2 Times in 2 Posts
Default

1. your web service should talk to the clients over SSL - encrypting the data being sent over the wire.

2. You can password protect a web service, requiring someone to login before giving out any data.


Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
web services tanzi C# 1 September 23rd, 2007 02:59 AM
Web Services BriTheProblem Book: Wrox's Visual C# 2005 Express Edition Starter Kit 1 May 11th, 2006 03:11 AM
Web Services Error (Ch18) - No Web Disc. Info. ElPato BOOK: Beginning ASP.NET 1.0 2 April 13th, 2005 03:27 PM
Web Services qadeerahmad .NET Web Services 1 August 7th, 2004 11:46 AM
Web Services qadeerahmad Forum and Wrox.com Feedback 3 August 7th, 2004 01:02 AM



All times are GMT -4. The time now is 05:47 AM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.