[jira] [Commented] (QPID-7247) Implement preferences model and REST API

["Keith Wall (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359001#comment-15359001 ] 

Keith Wall commented on QPID-7247:
----------------------------------

Reviewed implementation so far, no comments.

One comment against the API is that there is currently no reasonable way to get all preferences of a type belonging to a user.  Currently, the API demands that one calls the {{/userpreferences}} on every object to get a complete picture (n calls, where n is the number of objects).  If we supported wildcards {*} in name position(s) e.g. {{queue/*/*/userpreferences}}  then the number of calls would be reduced (m calls, where m is the number of categories) but this would still leave the UI having to make multiple calls, which seems unpleasant.    

> Implement preferences model and REST API
> ----------------------------------------
>
>                 Key: QPID-7247
>                 URL: https://issues.apache.org/jira/browse/QPID-7247
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>             Fix For: qpid-java-6.1
>
>
> Implement the preferences model and the REST API described by:
> https://cwiki.apache.org/confluence/display/qpid/Preference+Store
> After this work it will be possible to add/update/remove preference from the REST API, but there will be no persistence.  At this stage all preferences will be available to all users.   There will be no security in preferences layer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org