Hi,
I've just completed stage 1 of my research project. It took a little longer than expected, but I can now focus on the next stage. I am looking at integrating Web services into OpenACS. I know there is a SOAP-gateway package, and tclSOAP. I also know that none of these use tDOM as the XML parser. I wish to write my own SOAP interface using tDOM. Before venturing into the project I would like to hear from those that are interested in Web services, and have their own vision of Web services integration in OpenACS.
OpenACS has already moved from ns_xml to tDOM. Can anyone guarantee that we won't move to another XML parser? Would it be best to provide an interface to the XML parser, so that if we do change XML parsers we won't need to change a lot of code, just the interface bindings to the XML parser?
My end goal is to have a Web services package that sits on top of acs-service-contracts. This will allow a developer to export functionality through Web services by selecting specific service-contracts. I don't believe the existing SOAP-gateway package does this. The big picture that I have in mind is to use Web services as a way for dotLRN to comply to OKI. However the Web services package should be generic enough to export any registered acs-service-contract.
I'm working on a specifications document for this, and would like some feedback on this proposed project.
Regards,
Nick.