Ummm, you started this thread.
Nope, if I remember correctly, it was Malte starting the thread on remoting, by collecting some rough scenarios. I continued by summarizing what had been discussed during the OpenACS Spring Conference, still focussing on a general road mapping. It was you going into design + implementation details (of TWiST/tWSDL) which I somehow found inappropriate in a Future-of-OpenACS thread and therefore forked the original. However, my idea was still a general road mapping. C'est tout.
I listed the examples I could find, I asked for better examples. I'm still waiting.
Mmmh, if you are looking for "better examples" to the AXIS/.NET/... examples posted by you, simple googling won't be enough. I had good experiences with browsing the code repositories (especially the test suites contained in there) and getting my hands dirty with re-implementing and extending test cases for my purposes. If this is no option for you, mailing to the developer lists may help (that's why I indicated an example thread from the mono-devel list previously). At least, either of these options is better than posting a request to this forum.
What can be done? Have the most experienced people with regards to webservices (Stefan and Tom) along with interested OCT members come up with a generic strategy how to support webservices in OpenACS.
Taking up Malte's original statement, I would like to call a spade a spade. Tom, would you be willing to contribute (a) to a phase of general + detailed requirements gathering/ road mapping and, subsequently, (b) realising implementation efforts, even though they go beyond the scope of TWiST/tWSDL and might even replace these two as self-contained solutions?
