Hi, A couple of days ago Dave M. pointed out that ErlyWeb could benefit from a web services framework (in the thread about Strenghts and Weaknesses).
I would be willing to try to improve this, but I would like some guidance: what should it do? I will probably use the existing yaws+erlsom implication as a basis, but I agree that it can be improved. In particular the set-up could be easier. - I already have some code available that improves the handling of import statements. - What flavours of webservices should be supported? Currently we have the 'document/literal' type only. - What type of interoperability issues should I be aware of? - Should there be a strong link to the rest of erlyweb? What should it look like? Or would it be sufficient to offer support for web services in YAWS in a nice way? The handlers could call the ErlyDB APIs, of course. - Should there be a generic framework that also covers XMLRPC, REST, Json? Is there an example of such a framework - maybe in Ruby? I can imagine something generic for all the XML based variants, but I struggle for JSON. Not because it is not XML, but because there appears to be no 'schema' for JSON. It seems to me that such a framework would require some kind of metadata/specification, like a schema or WSDL. - anything else? Regards, Willem --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
