Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #10690 (new)

Opened 8 years ago

RFE: better handling of in certain write situations

Reported by: jamoore Owned by:
Priority: major Milestone: Unscheduled
Component: Services Version: n.a.
Keywords: n.a. Cc: mtbcarroll, jburel, bpindelski, wmoore, cxallan
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.




When the "" work around was created (#3527), it was designed for allowing the reading of all objects regardless of group but *wasn't* concerned with allowing writing from any group. In fact, it tries to prevent some actions, since miss linking objects between groups is a "bad thing".

More and more remote methods have been found which would *like* to use but require write permissions. In some cases, this has been handled server-side; in others, client-side by manually and temporarily setting the value to a specific group.

RawFileStore?.setFileId and RawPixelsStore?.setPixelsId are clear cases where the server *could* provide this functionality.


  • AbstractAmdServant? should have a method added (e.g. updateContext) which can be called if the setting is -1, and which looks up some reference object, whose group replaces -1 as the setting.
  • RawFileStore? and RawPixelsStore? set methods should be updated to use the AbstractAmdServant? method.
  • The save() and close() methods of both these methods may also need to take this value into account. If necessary, the return value of updateContext) can be stored in the servant implementation (e.g. RawFileStoreI) in order to use for all method invocations.

Change History (0)

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.77987 sec.)

We're Hiring!