[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xdi] $get operation helpers / enhancements
Markus, Yuriy Z. and TC:
>> I'm not sure if I fully understand the implications of distinguishing between binary If you are trying to browse a graph with 1000 pictures, your client will never return. In oxServer, we use the data URI format to specify type of the data. This enables us to return results either with or without the binaries, which was proven to be an absolute requirement for oxPlus. Note: I am suggesting this as a MAY feature, so if an XDI server wants to treat all literal values the same, that’s ok. $is$binary is a token with special meaning. We could put anything there or nothing. The idea is that we want to be able to list a return that you have pictures 1-1000, and then the client can choose which ones to download. $onelevel is a frequent requirement for browsing trees. I think we should prioritize the use cases that are needed first, and discuss enhancements later. We don’t need $level$2 right now, and in the last 20 years of LDAP history no one has. So why don’t we wait until we see the requirement, and then propose a new enhancement for semantics to support n level of searches. - Filtering by arc types makes sense to me. Maybe this could also be done using the syntax for variables, instead of introducing special $ words. Please give an example. I don’t understand your suggestion. Yes, and Giovanni’s filter requires an entire xdi statement. The syntax I suggesting is pretty simple pre-fix notation using the logical operators we already have defined: $and, $or, $not. You evaluate the parens and then combine according to the logical operator. And if we can put the filter directly in the $get operation, we don’t need variables: @!1111$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get($and(context=*friends*)(rel=*yuriy*))/@!4444 Using this method, we really cut down on the amount of graph that gets returned for a given request to a graph node. If we want to support variable substitution, I think this could be pretty straight forward: $get($and($1)($2)) ??? Would these variables definitions have to be in the same message? Also, maybe we should support an XRI reference to a filter defined in the graph: $get($and(xri(=mike+search1!)(xri(=mike+search2!))) - Mike
On Tue, May 22, 2012 at 7:31 PM, Michael Schwartz <mike@gluu.org> wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]