On Tue, 2001-12-18 at 14:42, Jochen Lillich wrote:
> Hi!
>
> I just had an idea: How about OI apps with XML-RPC or SOAP interfaces?
> How far are we from this as a reality? Is this only a matter of a
> SOAP-compliant OI handler?
This is actually on the SF feature request list[1]. I haven't attempted
this yet, but if I understand everything correctly here's how it would
be implemented:
(1) Create a SOAP conductor -- this would replace OI::UI::Main with
OI::UI::SOAP (or something, bad naming scheme)
(2) Name the conductor in your server configuration
(3) In an action you wanted to respond to SOAP requests, you'd specify
the SOAP conductor's name
(4) Instead of returning HTML content, I guess you'd pass off whatever
objects result from the request to the conductor, which would create the
response with the payload.
AFAICT, this is actually fairly simple and if I'd actually used SOAP
before (or had a paying customer needing it now) it would probably
already be in there :-)
Other ideas:
- Creating a service that advertises available SOAP methods would be a
snap since that information is already in the action table.(I can't
remember if this is UDDI, WDSL or some other acronym. I saw this at
Ziggy's presentation at YAPC::NA and it immediately made sense, so it
can't be too hard :-)
- Create a simple SOAP gateway for SPOPS objects. This would be pretty
cool because you can not only retrofit an object mapping to one or more
relational tables very quickly, you can expose that mapping to many
languages at once. (Potentially impressive demo tool :-) The other
benefit is that 'SOAP-SPOPS' uses only three letters...
Chris
[1]http://sourceforge.net/tracker/index.php?func=detail&aid=468934&group_id=16810&atid=366810
--
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.
|
