Diff between Coldfusion web service and a regular page

Hello,

I am creating an small app to accept an http request (non SOAP) from another company. This request will be a form post, the form fields will be processed and either a 1 or 0 should be returned. I was thinking about doing this as w web service but I have some basic questions.

Is there an advantage of using a web service vs. a regular .cfm page to process the request?

When you create the WS in CF8 is there a way to tell it that a username and passwd is required to access the web service? The username/pwd in the CF admin page does not do this, actually, I am not sure what that unm/pwd are for because it does not seem to effect consuming the web service or accessing the WS in the cfasmin. I can require that username/pw fields be passed in the form and check that but how would that be different from a regular web page?

Thanks.

Joe
ckercherAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ckercherAuthor Commented:
Actually, you don't even need to create the web service in CF admin. Just create the CFC and access it.
0
micropc1Commented:
Right - its just a normal CFC - you just interact with it differently. This might be useful...
http://help.adobe.com/en_US/ColdFusion/9.0/Developing/WSc3ff6d0ea77859461172e0811cbec22c24-78a6.html
0
digicidalCommented:
In the case of a non-SOAP request you would want to simply use a normal page (although you could certainly design a CFC to handle the request as well).  Since you are receiving a plain HTML form post with limited 'call-response' behavior - I would simply make a page to handle that request.  It seems that you are simply taking input and storing that information for retrieval by another application/system/db etc..  It's certainly up to you, but I would just keep it simple.  You can always wrap the process up into a WS later on if you need to have more bi-directional communication with the intended data originator (the one sending the post).

For the most part, a WS is like a miniature application in itself.  They're great for allowing remote applications to query a database on your server, or provide status updates and move more complex information back and forth.  For example, if you wanted your application to return an array of all the submitted data and a status message related to each field on the form individually... you would want a WS.  If you simply want to allow an HTML form to be posted to a page which then either says "YAY" or "BOO" in response... just use a page for that.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ckercherAuthor Commented:
Thanks for your inputs. I do not really see an advantage to using a WS so I am just creating a regular page to process these requests.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ColdFusion Language

From novice to tech pro — start learning today.