Hi all, I'm almost done with template matching for request URL in RESTful Services. However, I have left out the Query String when I do the matching for the moment.
This is due to several reasons. 1. The query parameters are already made available on the generated payload. 2. The order of params in the Query String is insignificant (am I missing something here?) and thus it is very much resource consuming, and inefficient to do sorting before template matching. Therefore, during the matching process I only consider the portion before the '?' character in both the template as well as the URL. There are several disadvantages in this process. 1. The user can't have something like this. ex:- GET:op/param?a=1&b=2 and GET:op/param?a=1 which maps to two operations if we use the same HTTP Method. 2. The user can't have something like this. ex:- GET:op/param?a=1&b=2 and GET:op/param?a=1&c=2 which maps to two operations if we use the same HTTP Method. The reason to this issue is that the best fit matching mechanism will choose either 1 or 2, depending on the ordering of the operations on the services.xml. I thought of Implementing this on a later date depending on the requirement. Any thoughts? Regards, Senaka --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
