Pros: 1) Very easy to get started 2) Part of the Umbraco architecture, so easy for anyone familiar with Umbraco and not explicity webservices to understand.
Cons: 1) Reliance on the Umbraco architecture - not great if your service isn't touching anything on the website. Use standard REST or WCF service? This link may also leave you open to abuse if any bugs are found in the /base code or architecture that could be exploited. 2) No built in request authorisation - you'll need to check where requests are coming from any authorise them. 3) Limited when compared to a fully-blown webservice (such as a WCF service) - so may have limited potential for growth.
I'd recommend that if you're building a public webservice you go with WCF. If you're wanting to knock up a service you can call from the website itself, such as to AJAX post forms to, then /base is good.
Using /Base as public webservice?
What are pro and con for using /Base as a public webservice?
Pros:
1) Very easy to get started
2) Part of the Umbraco architecture, so easy for anyone familiar with Umbraco and not explicity webservices to understand.
Cons:
1) Reliance on the Umbraco architecture - not great if your service isn't touching anything on the website. Use standard REST or WCF service?
This link may also leave you open to abuse if any bugs are found in the /base code or architecture that could be exploited.
2) No built in request authorisation - you'll need to check where requests are coming from any authorise them.
3) Limited when compared to a fully-blown webservice (such as a WCF service) - so may have limited potential for growth.
I'd recommend that if you're building a public webservice you go with WCF.
If you're wanting to knock up a service you can call from the website itself, such as to AJAX post forms to, then /base is good.
Cheers,
Drew
is working on a reply...