Re: Do web services make sense for me?
From: Ron L (ronl_at_bogus.Address.com)
Date: 11/02/04
- Next message: SQLScott: "config Files and Sensitive Info"
- Previous message: GreyAlien007: "Re: Windows API (NetUserChangePassword)"
- In reply to: Cor Ligthert: "Re: Do web services make sense for me?"
- Next in thread: chanmmn: "Re: Do web services make sense for me?"
- Reply: chanmmn: "Re: Do web services make sense for me?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 2 Nov 2004 11:06:36 -0500
Cor
As far as I can tell, I will still need to give the users access to my
database (at least as far as SQL is concerned), because I have to have the
users accessing it under their own login. This is due to the "filter"
requirement I alluded to. I have a table that effectively reads <username>
can read this class, can create that class, can edit a third class, and
can't even see the remaining classes. Because of this, I have to grant each
user access to the database and use integrated authentication - as far as I
can tell, this means that my Web Services classes will effectively mimic my
SP list. The only thing I can see that it might do is not include any
entries for SPs that general users need to run (administrative SPs). I'm
not sure that the extra layer is worth this minor gain
Thanks for your response.
Ron L
"Cor Ligthert" <notmyfirstname@planet.nl> wrote in message
news:Ow4H$IPwEHA.1300@TK2MSFTNGP14.phx.gbl...
> Ron,
>
> In my opinion there is the most important advantage by adding a webservice
> is that you can close your database completly for the outside world.
>
> You only give the data that is requested without any connection to that
> database.
>
> Or did I understand your question wrong?
>
> Cor
> "Ron L" <ronl@bogus.Address.com>
> ...
>>I have an existing ASP/ MSSQL project that we are looking at migrating to
>>VB.Net (standalone app, not ASP) which will still interact with a single
>>central SQL server. Because we have a requirement to "filter" data
>>returned depending on the user's permission to certain classes of data we
>>hava all access implemented via stored procedures. Another reason for
>>using SPs is that certain tables have a requirement to keep track of who
>>made changes, what the change was (old and new data), and when the change
>>happened. Given these requirements, it appears to me that adding a web
>>service simply inserts another layer between the user and the database,
>>and one that is going to require that I define a Command object for each
>>stored procedure call. Are there advantages that I am not seeing, or am I
>>better off just having my application create the necessary data objects
>>that directly query the database?
>>
>> TIA
>> Ron L
>>
>
>
- Next message: SQLScott: "config Files and Sensitive Info"
- Previous message: GreyAlien007: "Re: Windows API (NetUserChangePassword)"
- In reply to: Cor Ligthert: "Re: Do web services make sense for me?"
- Next in thread: chanmmn: "Re: Do web services make sense for me?"
- Reply: chanmmn: "Re: Do web services make sense for me?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|