I just wonder why is it not recommendet not to use GUI in web services.
You use GUI in ASP.NET all the time so why can't you use it in Web services.
//Tony
If needed you could have a UI that uses your lower level services to have
something out of the box. If still allows others to built their own UI as
needed. If you just want t UI, this is just an ASP.NET website...
--
Patrice
"Tony Johansson" <johansson...@telia.com> a �crit dans le message de
news:LG%Zm.13985$U5.2...@newsb.telia.net...
> I just wonder why is it not recommendet not to use GUI in web services.
> You use GUI in ASP.NET all the time so why can't you use it in Web
> services.
Because that's not what a web service is!
Think of it like any other class library, i.e. a collection of methods which
can be incorporated into other solutions as required. The only difference
between a web service and a class library, as far as the solutions which use
it are concerned, is how they reference it...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
> I just wonder why is it not recommendet not to use GUI in web
> services. You use GUI in ASP.NET all the time so why can't you use it
> in Web services.
A web service is a type of UI, in and of itself. It is not a GUI type of
UI, but that is because it is set up to be a data boundary. In general,
you do not have users directly accessing a web service.
In many ways, this is like asking, why not make a GUI on top of SQL
Server or Oracle. Because the GUI is farther up the line.
You can set up the following:
UI <> Web Service <> Business Library <> Data Layer <> Data Storage
or
UI <> Business Library <> Web Service <> Data Layer <> Data Storage
Hope this helps.
Peace and Grace,
--
Gregory A. Beamer (MVP)
Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com
*******************************************
| Think outside the box! |
*******************************************