On Wed, Nov 22, 2017 at 9:38 AM, Menuka Warushavithana <[email protected]> wrote:
> Hi all, > After debugging, it became clear that the query sent from client is > decoded by the MSF4J service. So it only needs to be properly encoded by > the client-side. Thanks for the insights! > What is the apporach you are going to use in client side to encode this ? > > Regards > > *Menuka Warushavithana* > *Software Engineering Intern* > *WSO2* > > *Mobile: + <%2B%2094%2011%202145345%20%C2%A0Ext.%205737> 94776979690* > *LinkedIn: **https://www.linkedin.com/in/menukawarushavithana/ > <https://www.linkedin.com/in/menukawarushavithana/>* > *GitHub: **https://github.com/menuka94/ > <https://github.com/menuka94/>* > > > > On Thu, Nov 16, 2017 at 2:07 PM, Samitha Chathuranga <[email protected]> > wrote: > >> Hi Menuka, >> >> >>>>> - Even though the character '&' is used for separating fields >>>>> (for clear representation), it's confusing to use '&' in the URL as >>>>> it's >>>>> used for separating GET parameters. So what should be the delimiter to >>>>> be >>>>> used in place of '&' ? [ I'm suggesting "," (the comma) ] >>>>> >>>>> In this case IMO you can encode the pattern in the URL and send. [1] >>> >>> [1] - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe >>> rence/Global_Objects/encodeURIComponent >>> >> >> Using either & or comma is ok AFAIU, but it is important to use encoding >> as mentioned in [1]. (can effect in security issues later if not). Can >> decode back with [2] when using the passed values. >> >> [2] - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe >> rence/Global_Objects/decodeURIComponent >> >> Regards, >> Samitha >> >> On Tue, Nov 14, 2017 at 3:00 PM, Chamin Dias <[email protected]> wrote: >> >>> Hi Menuka, >>> >>>> >>>>>> - Should there be a limit to the number of attributes? i.e. Do we >>>>>> need to support a query like "name:sampleapi&version:1.0.0& >>>>>> provider:admin&LifeCycleStatus:created" where four attributes are >>>>>> used for querying? >>>>>> >>>>>> If you need a search based on "name of the API AND the version of the >>> API" only, then we can get data by using AM_API table solely. If the search >>> goes to other tables such as AM_API_TAG_MAPPING (Eg : >>> name:sampleapi&version:1.0.0&tag:wso2), then only we need to modify the >>> queries IMO. >>> >>> Thanks. >>> >>> -- >>> Chamin Dias >>> Mobile : 0716097455 >>> Email : [email protected] >>> LinkedIn : https://www.linkedin.com/in/chamindias >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Samitha Chathuranga >> Software Engineer, WSO2 Inc. >> lean.enterprise.middleware >> Mobile: +94715123761 >> >> [image: http://wso2.com/signature] <http://wso2.com/signature> >> > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
