[Bug 2213] [STORY] Rework Web API

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2213

Jie Kang <jkang at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jkang at redhat.com

--- Comment #1 from Jie Kang <jkang at redhat.com> ---
In terms of url access paths and data format, another alternative is to map
them directly to the collections.

/storage/{collection-name}
GET /storage/vm-info :: gets all entries in vm-info
POST /storage/vm-info :: adds a new entry in vm-info

The vmID/agentID/hostname in the URL is unnecessary as the collections aren't
separated this way and the entries contain this data. The downside is it is
more difficult to have authorization based on this data.

More enhanced queries could also be supported server-side such as filtering

/storage/{collection-name}/{field}/{value}
GET/storage/vm-info/vmId/avmid :: gets all entries where field 'vmId' matches
'avmid'

This probably needs thought as it's currently limited to filtering over a
single field. The easiest way is to include such data within the request, which
the server-side then parses, but I would much prefer not doing so.

The server-side support for enhanced query API should be carefully restricted
for security and lower workload, as client's can manipulate data as well. At
the same time, enhanced queries can dramatically reduce the amount of data
being transferred.


Integration alongside the current Web API also needs consideration. Current
users access data through DAO objects where the actual implementations of data
acquisition are hidden. This system should probably be maintained such that the
use of the new or old Web API can happen underneath, without changing the calls
users make of the DAO objects. New access methods can be provided as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20161110/7ae97272/attachment-0001.html>