Search results

plone.jsonapi.core-0.5-1.lbn19.noarch

Abstract An extensible Plone JSON API Framework Introduction This Package allows Users to expose content information via JSON. Motivation This project was born in 2012, out of the need for a data source to build a network based iOS application. Or more precise, I wanted to learn iOS programming and wanted to knit my own JSON API:) I know, it is a little bit awkward to provide an own routing mechanism for Plone which dispatches the request after the ZPublisher did its job, but it worked and thus, I did it. Limitations Since the API comes after the ZPublisher, it can only make use of HTTP GET and HTTP POST methods. The other methods will never reach the API View. Be aware that the API View comes with the permission zope2.View, so you need to programmatically check for the correct permissions on your custom routes.

plone.jsonapi.core-0.5-1.lbn25.noarch

Abstract An extensible Plone JSON API Framework Introduction This Package allows Users to expose content information via JSON. Motivation This project was born in 2012, out of the need for a data source to build a network based iOS application. Or more precise, I wanted to learn iOS programming and wanted to knit my own JSON API:) I know, it is a little bit awkward to provide an own routing mechanism for Plone which dispatches the request after the ZPublisher did its job, but it worked and thus, I did it. Limitations Since the API comes after the ZPublisher, it can only make use of HTTP GET and HTTP POST methods. The other methods will never reach the API View. Be aware that the API View comes with the permission zope2.View, so you need to programmatically check for the correct permissions on your custom routes.

plone.jsonapi.routes-0.8.4-1.lbn19.noarch

Introduction This is an add-on package for plone.jsonapi.core which provides some basic URLs for Plone standard contents (and more). Motivation The routes package is built on top of the plone.jsonapi.core package to allow Plone developers to build modern (JavaScript) web UIs which communicate through a RESTful API with their Plone site. Compatibility The plone.jsonapi.routes should work with Plone 3 and 4. API URL After installation, the Plone API routes are available below the plone.jsonapi.core root URL (@@API) with the base /plone/api/1.0, for example http://localhost:8080/Plone/@@API/plone/api/1.0/api.json. There is also an overview of the registered routes which can be accessed here: http://localhost:8080/Plone/@@API/plone/api/1.0/api.json API Routes BASE_URL: /plone/api/1.0 This is an overview of the provided API Routes. The basic content routes provide all an interface for CRUD operations. CRUD URL Scheme: OPERATION URL METHOD PAYLOAD VIEW <BASE_URL>/<RESOURCE>/<uid:optional> GET -- CREATE <BASE_URL>/<RESOURCE>/create/<uid:optional> POST JSON UPDATE <BASE_URL>/<RESOURCE>/update/<uid:optional> POST JSON DELETE <BASE_URL>/<RESOURCE>/delete/<uid:optional> POST JSON

plone.jsonapi.routes-0.8.4-1.lbn25.noarch

Introduction This is an add-on package for plone.jsonapi.core which provides some basic URLs for Plone standard contents (and more). Motivation The routes package is built on top of the plone.jsonapi.core package to allow Plone developers to build modern (JavaScript) web UIs which communicate through a RESTful API with their Plone site. Compatibility The plone.jsonapi.routes should work with Plone 3 and 4. API URL After installation, the Plone API routes are available below the plone.jsonapi.core root URL (@@API) with the base /plone/api/1.0, for example http://localhost:8080/Plone/@@API/plone/api/1.0/api.json. There is also an overview of the registered routes which can be accessed here: http://localhost:8080/Plone/@@API/plone/api/1.0/api.json API Routes BASE_URL: /plone/api/1.0 This is an overview of the provided API Routes. The basic content routes provide all an interface for CRUD operations. CRUD URL Scheme: OPERATION URL METHOD PAYLOAD VIEW <BASE_URL>/<RESOURCE>/<uid:optional> GET -- CREATE <BASE_URL>/<RESOURCE>/create/<uid:optional> POST JSON UPDATE <BASE_URL>/<RESOURCE>/update/<uid:optional> POST JSON DELETE <BASE_URL>/<RESOURCE>/delete/<uid:optional> POST JSON

plone.jsonserializer-0.9.7-1.lbn25.noarch

JSON serialization/deserialization adapters for Plone.

plone.jsonserializer-0.9.7-1.lbn25.noarch

JSON serialization/deserialization adapters for Plone.

plone.keyring-2.0.1-2.lbn13.noarch

*plone.keyring* contains a Zope3 utility that facilitates handling of secrets in an application. Secrets are very important in modern applications, which is why a shared tool to manage them is useful. plone.keyring contains two basic components: * a *keyring*: a data structures which contains one or more secrets. * a *key manager*: a utility which contains the available keyrings and provides some convenience methods to manage them Keyrings ======== The keyring is the workhorse: it contains a set of secrets for a specific purpose. A ring has room for a fixed number of secrets which is set at creation time. The most recently added secret is considered to be the 'current' secret and the one that should be used. Older secrets in the ring can be used to keep data generated with older secrets valid for a period of time. Key manager =========== The key manager is a container for the available keyrings. It always contains a default system keyring which is used when no other ring is explicitly requested.

plone.keyring-3.0.2-1.lbn25.noarch

*plone.keyring* contains a Zope3 utility that facilitates handling of secrets in an application. Secrets are very important in modern applications, which is why a shared tool to manage them is useful. plone.keyring contains two basic components: * a *keyring*: a data structures which contains one or more secrets. * a *key manager*: a utility which contains the available keyrings and provides some convenience methods to manage them Keyrings ======== The keyring is the workhorse: it contains a set of secrets for a specific purpose. A ring has room for a fixed number of secrets which is set at creation time. The most recently added secret is considered to be the 'current' secret and the one that should be used. Older secrets in the ring can be used to keep data generated with older secrets valid for a period of time. Key manager =========== The key manager is a container for the available keyrings. It always contains a default system keyring which is used when no other ring is explicitly requested.

plone.keyring-3.0.2-1.lbn25.noarch

*plone.keyring* contains a Zope3 utility that facilitates handling of secrets in an application. Secrets are very important in modern applications, which is why a shared tool to manage them is useful. plone.keyring contains two basic components: * a *keyring*: a data structures which contains one or more secrets. * a *key manager*: a utility which contains the available keyrings and provides some convenience methods to manage them Keyrings ======== The keyring is the workhorse: it contains a set of secrets for a specific purpose. A ring has room for a fixed number of secrets which is set at creation time. The most recently added secret is considered to be the 'current' secret and the one that should be used. Older secrets in the ring can be used to keep data generated with older secrets valid for a period of time. Key manager =========== The key manager is a container for the available keyrings. It always contains a default system keyring which is used when no other ring is explicitly requested.