Re: No asmx filename
- From: "Patrice" <http://www.chez.com/scribe/>
- Date: Thu, 23 Oct 2008 09:44:07 +0200
If the ASMX choice was done on purpose this is really something you don't
care. You just have to point your dev tool to a *single* url and all the
plumbing is done for you so IMO exposing several URLs is even counter
productive...
If this is an URL that clients are using explicitely then an ASMX service is
perhaps not the best choice. I'm still green about that but WCF offers AFAIK
more flexibility allowng either to exposes a whole service or explicit
URls...
IMO you should first make sure how you intend this service to be consumed.
--
Patrice
"BonesBrigadier" <a@xxxxx> a écrit dans le message de groupe de discussion :
O0vBQvINJHA.3764@xxxxxxxxxxxxxxxxxxxxxxx
One WebService with 4 WebMethods.
I want to expose several methods using same URL. Something like:
services.whatever.com/webmethod1
services.whatever.com/webmethod2
services.whatever.com/webmethod3
services.whatever.com/webmethod4
Might be a REST style service. I will read a lot more about all this.
Regards,
G
.
- References:
- No asmx filename
- From: BonesBrigadier
- Re: No asmx filename
- From: John Saunders
- Re: No asmx filename
- From: BonesBrigadier
- Re: No asmx filename
- From: John Saunders
- Re: No asmx filename
- From: BonesBrigadier
- Re: No asmx filename
- From: Patrice
- Re: No asmx filename
- From: BonesBrigadier
- No asmx filename
- Prev by Date: Convert Form Post to VB.NET HTTPWebRequest code and Catch Response
- Next by Date: Re: Convert Form Post to VB.NET HTTPWebRequest code and Catch Response
- Previous by thread: Re: No asmx filename
- Next by thread: Re: No asmx filename
- Index(es):
Loading