Hi Gaurav, how would you use the returning RIDs? May you post an example here?
Lvc@ On 11 March 2014 20:12, Gaurav Dhiman <[email protected]> wrote: > > > On Tue, Mar 11, 2014 at 5:47 PM, Luca Garulli <[email protected]> wrote: > >> Sorry I meant the # can be omitted in RIDs. >> > > Yes, to omit that, client need to do processing of JSON received from > server, which I feel is overhead for large JSON stream. > Can not we avoid # all together in JSON pushed by server. > > Regards, > Gaurav > > >> Lvc@ >> >> >> On 11 March 2014 18:59, Gaurav Dhiman <[email protected]> wrote: >> >>> >>> On Tue, Mar 11, 2014 at 5:14 PM, Luca Garulli <[email protected]>wrote: >>> >>>> Hi, >>>> on REST calls all the RID on URL can be omitted. >>>> >>> >>> RID segment in document REST call is mandatory as per this >>> https://github.com/orientechnologies/orientdb/wiki/OrientDB-REST#wiki-get---document. >>> We can not omit that. Otherwise also I think # will create issues in other >>> REST calls. >>> >>> Gaurav >>> >>> >>>> Lvc@ >>>> >>>> >>>> >>>> On 11 March 2014 18:31, Gaurav Dhiman <[email protected]> wrote: >>>> >>>>> I am sure many users of orient must have face this challenge. Kindly >>>>> suggest simplest way to handle. >>>>> >>>>> Scenario: >>>>> 1. Calling server function over REST >>>>> 2. Server returns multiple records of a class with # in RIDs >>>>> 3. Client user received RIDs to make further REST document calls, but >>>>> due to # chanracter presence, calls go without RID argument >>>>> >>>>> Due to # character, call to >>>>> *http://<<host>>:<<port>>/document/<<db>>/#RID* is considered as >>>>> *http://<<host>>:<<port>>/document/<<db>>* >>>>> >>>>> Workaround: >>>>> While receiving response from server, remove all # characters from >>>>> response, but this add un-required processing. It would have been better >>>>> if >>>>> # has not been there. >>>>> >>>>> Question: >>>>> What is the significance of having # in RID ? Can't we get rid of it ? >>>>> If yes, how ? >>>>> >>>>> Regards, >>>>> Gaurav >>>>> >>>>> -- >>>>> >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "OrientDB" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "OrientDB" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/orient-database/IIM-qv29-ZE/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "OrientDB" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "OrientDB" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/orient-database/IIM-qv29-ZE/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
