Hi Jeremy,

The new REST API has been successfully used by several projects and we
definitely plan to consider it a formal (non-experimental) part of the
repository service going forward.  The current plan is to do this for
the next release, 3.2, which is scheduled for early Spring (no firm
date 'till we get closer).  This release will also include some
updates to the implementation, including the following:

https://fedora-commons.org/jira/browse/FCREPO-410
https://fedora-commons.org/jira/browse/FCREPO-412

On the security side, there was formerly an issue (now fixed) where
authentication wasn't being executing correctly:
https://fedora-commons.org/jira/browse/FCREPO-241
For authorization, I verified for another project recently that XACML
access policies are being respected when coming through this API.

- Chris

On Wed, Feb 18, 2009 at 4:54 PM, Gottwig, Jeremy M. (GSFC-272.0)[ZAI]
<[email protected]> wrote:
> I'm just starting doing some frontend development, and I've been thinking of
> using the REST API, but I'm a little concerned about some of the stuff I
> read here in the introduction:
>
> http://fedora-commons.org/confluence/display/FCR30/Fedora+REST+API
>
> I know some time has passed since this was published, so I'm curious if the
> REST API has yet gone through any security testing by anyone either directly
> or indirectly related to the project.  Also, is there a timeline for when it
> will be considered a stable feature?

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to