[
https://issues.apache.org/jira/browse/WOOKIE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921149#comment-13921149
]
Scott Wilson commented on WOOKIE-414:
-------------------------------------
I think the best way to implement this is for all POST and PUT operations to
send JSON in the body of the request containing all the properties they want to
set. I've got this working in my local copy, I just need to add some more tests.
> Decrease preferences protocol overhead
> --------------------------------------
>
> Key: WOOKIE-414
> URL: https://issues.apache.org/jira/browse/WOOKIE-414
> Project: Wookie
> Issue Type: Improvement
> Reporter: Michael Aram
> Priority: Minor
> Fix For: 2.0.0
>
>
> Consider a use case, where you automatically embed Wookie widgets and have to
> configure them a bit. Think of a news reader widget that gets a concrete news
> feed URL set as a parameter on startup.
> The problem with the current API is, though, that it allows us only to set
> parameters one by one. This results in a unnecessary network overhead, as the
> container has to send e.g. 6 HTTP requests (for a widget with 5 preferences)
> to Wookie before being able to deploy the Wookie-Widget-Instance-URL of the
> correctly configured widget-instance to the users browser. (Another, minor
> problem is the existence of an unconfigured or partly configured widget
> instance in the course of this transaction.)
> Therefore, I propose to extend the REST API so that it allows one to send an
> additional JSON (member) object containing widget properties when
> instantiating a widget. Resulting in 1 HTTP request only between container
> and Wookie.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
