"Oh, the joy of automating FORM POST ops, the FORM POST ops, the FORM POST ops.
Fa la la la la ...":)~
What we have here is the need for a SOAP Service Gateway. A minimal implementation should include and not necessarily limited to:
- WSDL spec generator that distills public package methods.
- Interface stub generator for popular languages (C/C++ and Java).
- SOAP service gateway/codec for op propagation.
My problem is that I know too little about OpenACS and shudder at the thought of making critical recommendations to its architecture. I will be investigating integration of existing Tcl SOAP solutions into the OpenACS environment and attempt to bridge the logic at my own risk.
I state with the utmost confidence that SOAP integration into OpenACS will elevate it to a significantly more powerful solutions paradigm. The ability to leverage the innovative packages included with OpenACS using SOAP RPC gives developers, users, and business interests new tools that will expedite the utilization of the solutions OpenACS provides. If implemented, SOAP based Web Services should occupy the front pages of the OpenACS tabloids. It would be awesome!
I'd be happy to offer input. My background includes the design and management of a commercial M/T app server that incorporates a SOAP/HTTP codec, stub generator, dynamic WSDL port RPC paths, etc. If anyone is interested, let's talk. My time requirements mandate a hack implementation; however, a formal project might not be a bad idea.
