Thanks, Nuwan. Ayoob, both these resources are valid for the request you are sending. You > can't say one is wrong and the other is right. What you're expecting is > like a best match scenario, which synapse doesn't support at the moment. It > should be possible to implement it using a scoring mechanism or something > like that, but it'll definitely impact performance. > > From a REST point of view, its an invalid design. So my question is why > bother anyway? Do you really have resource paths that are impossible to > determine at design time? > We do have a root resource name which is binded to the api endpoint context.
I think since we have a restriction to support the best matching, its best for us to go through our api design to cater the way that synapse is supporting. Thanks
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
