[ic] Using Interchange as a SOAP server

[Mike Heins]

Quoting Dr. Michael Streubel (michael.streubel at ibizplanet.com):
> 
> 
> Mike Heins wrote:
> 
> >Quoting Chris Sendall (cjs2 at admin.cam.ac.uk):
> > 
> >
> >>If there are no SOAP_Control definitions in interchange.cfg then the 
> >>catalog.cfg
> >>is not checked
> >>   
> >>
> >
> >Exactly as designed. Since the SOAP module allows direct subroutine
> >calls to the Interchange core, we don't want to allow them unless
> >they are specifically enabled.
> >
> >If you want a promiscuous server then you need to put in interchange.cfg:
> >
> >	SOAP_Control Tag  always
> >
> >If you wanted to prevent only a few tags you would do:
> >
> >	SOAP_Control Tag 	    always
> >	SOAP_Control Tag/writefile  never
> >	SOAP_Control Tag/dangerous  never
> >
> > 
> >
> Thanks for elucidating. But how about the reverse? I want a server with 
> closed borders,
> but only one of my catalogs opens the door for a specific tag.
> 
> If, in the global config, you say
> 
>             SOAP_Control Tag local
> 
> then the catalog config doesn't have any impact.

I don't see that as a true statement. If you have that, then

	Tag/writefile  never
 
in the catalog.cfg should still disable the "writefile" tag.

I could see how it would be nice to have the "local" enforced 
over the "always", but I still think it works as was intended.

That being said, I am certainly open to argument that it needs
to be changed.

> If you say
> 
>        SOAP_Control Tag never
> 
> you're done and if you don't say anything in the global config, existing 
> code doesn't look at the catalog config any more.

Again, that is as intended. It allows you to totally disable Tag
capability in the global SOAP configuration.

-- 
Mike Heins
Perusion -- Expert Interchange Consulting    http://www.perusion.com/
phone +1.765.647.1295  tollfree 800-949-1889 <mike at perusion.com>

Being against torture ought to be sort of a bipartisan thing.
-- Karl Lehenbauer