Re: [SOAP] Generic Database Access

> I'll be more than happy to accept correction if I'm wrong, but isn't this the > drawback to soap? I mean, not every protocol is cut out for every type of data > transfer. Besides, I think the idea of a soap rpc is to abstract it more than > you are doing: i.e. the soap client shouldn't care if there's a database, flat > file or a hashtable on the server end. > > However, everyone has different needs, and not all systems fit all needs. Perhaps > you could make a single string value in the soap return values that contained a > comman (or other) seperated list. While that's not 100% cross-platform portable, > it's a close as you can easily get without adding a lot of overhead. You could > also include a soap structure that contained the number of fields/rows and the > data type of each column. This would make it easier to parse the string. This was what I was thinking I was going to have to do. I was just hoping that someone out there had been through this hell before and found a better solution. Thanks for the input, Rob