mlw writes:
On the flip side, I am also working on a PostgreSQL SOAP interface,
where one does this:
http://somehost/postgresql?query=select * from table
And a SOAP compatible resultset is returned.
That looks quite similar to the planned XML functionality. While that
plan doesn't contain
I have been working on moving some of my software to a more SOAP
compatible interface. As I was doing it, it occured to me that a generic
function could be written, in PostgreSQL's new function manager that
allows multiple columns to be returned, that is a generic SOAP interface.
All one would
First, a SOAP query should be posted in SOAP message format, not using the
query string as you do. Second, I like the idea of calling external SOAP
services, but consider creating a language 'soap' you could do with a CREATE
FUNCTION type thing. e.g.
CREATE FUNCTION foo (TEXT) RETURNS INTEGER AS
Jason wrote:
If you can support xmlrpc instead, you'll save yourself a lot of headaches.
XML-RPC has three merits over SOAP:
1. It's a simple specification, and thus readily implemented.
2. Microsoft and IBM aren't fighting over control over it, so it's
not suffering from the we keep
On Fri, Mar 28, 2003 at 01:36:43PM -0500, [EMAIL PROTECTED] wrote:
Of course, CORBA has actually been quite formally standardized, suffers
from many fairly interoperable implementations, and is rather a lot less
bloated than any of the XML-based schemes. It might be worth trying,
too...
The
Jason M. Felice wrote:
First, a SOAP query should be posted in SOAP message format, not using the
query string as you do. Second, I like the idea of calling external SOAP
services, but consider creating a language 'soap' you could do with a CREATE
FUNCTION type thing. e.g.
CREATE
On Fri, 2003-03-28 at 14:39, mlw wrote:
I was thinking of using SOAP over HTTP as the protocol, and a
minimalist version at best. If the people want more let them add it.
I have an HTTP service class in my open source library. It would br
trivial to accept a SQL query formatted as a GET
