Remote API
Motivation
Remoting API and/or framework (through SOAP Web Services, REST, WCF, XML-RPC, protobuffers, U name it) for:
- remote maintenance
- batch editing/work
with: Nice-to-have to reuse existing Composite C1
- CRUD stuff (all Ops - select, insert, update, delete)
- for CRUD stuff security is essential (authentification/authorization API)
Idea is to reuse Composite C1 exisitng authentification/authorization API.
References
Documentation:
- Fronetnd FAQ - External functions - ASHX files:
http://docs.composite.net/HTML/FrontendFAQ?q=Can+I+call+C1+Functions+AJAX+style+from+JavaScript+or+Flash%3F
Caveat: "Read only" - CRUD needed with authentification and authorization
Suggestions?
Discussion list:
- http://compositec1.codeplex.com/discussions/263317
- http://compositec1.codeplex.com/discussions/263678
- http://compositec1.codeplex.com/discussions/256876
- http://compositec1.codeplex.com/discussions/250644
Status
- Implemented External Function with ashx
:
Bugs/features found: External Functions ashx - lowercase url - excption http://www.holisticware.net/HolisticWare/Know-How/development/Web/CMS/Composite-C1/Discussions/2012-03-07-External-Functions-ashx-lowercase-url-excption.aspx - Implemented SOAP webservice
- in root of the application: http://host.domain/api/tools.asmx
Works OK, but no security - behind/below Composite of the application: http://host.domain/Composite/api/tools.asmx
Currently getting redirects, but working on it!
Before going further, any suggestions/ideas. Composite C1 uses SOAP a lot this would be nice-to-have...
- in root of the application: http://host.domain/api/tools.asmx