> I would suggest that you create an RpcSoap directoory in > qooxdoo-contrib and put, at a minimum, a README file containing a link > to the soap project. That way, when people are looking for an RPC > implementation, they'll see it. All other RPC implementations in > qooxdoo-contrib are RpcSomething, so creating that directory and > readme will make it much more obvious.
I'm not so sure about that. If I got it right, Burak's Soap server needs specific JavaScript Soap classes on the client side to talk to. So, if I got that right, it doesn't fit straight in the row of backends that work interchangeably with the standard qooxdoo RPC client classes. I think the Soap contrib is an *alternative* transport mechanism, and adding a RpcSoap contrib would actually mislead people in believing that would work with vanilla qooxdoo RPC classes. T. > > Derrell > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
