Example service #126
Closed
Example service #126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
To run: $ cd /path/to/islandora/services/TransactionService
$ curl -sS https://getcomposer.org/installer | php
$ php composer.phar install
$ cd src
$ php -S localhost:9999 index.php |
| $app['debug'] = true; | ||
|
|
||
| $app['fedora'] = function () use ($app) { | ||
| $client = new Client(['base_uri' => 'http://127.0.0.1:8080/fcrepo/rest']); |
There was a problem hiding this comment.
Still new to this stuff, is there a reason you didn't use the static constructor with the base_uri and get back the Chullo?
ie.
return Chullo::create('http://127.0.0.1:8080/fcrepo/rest');
There was a problem hiding this comment.
No reason in particular. Doing it manually gives you a bit more control over the client, which in this case, is unneccessary.
| "/islandora/transaction/{id}/rollback", | ||
| function (Application $app, $id) { | ||
| try { | ||
| return $app['fedora']->rollbackTransaction($id); |
There was a problem hiding this comment.
Probably should remove this 'return'
This was referenced Dec 8, 2015
…edoraApi class from Chullo.
Depends on Chullo fixes at https://github.com/DiegoPino/chullo/tree/api
for get route: assuming it's running in 8181 (example php -S localhost:8181 -t src src/index.php ) then http://localhost:8181/islandora/resource/7ef68f6f-72ab-4708-b0f4-8ec1f07 cd580 will get the resource for a resource that has nfo:uuid -> 7ef68f6f-72ab-4708-b0f4-8ec1f07cd580 in the triple store and http://localhost:8181/islandora/resource/7ef68f6f-72ab-4708-b0f4-8ec1f07 cd580/OBJ will get the child resource for that one (in this case binary) Accepts also a ?tx=transactionid * if the transactionid does not exist if fails with 404 * if uuid is not uuid then it fails with 404 * if resource path is not in triple store if fails with 404
Main route for getting a resource accepts also a metadata argument localhost:8181/islandora/resource/7ef68f6f-72ab-4708-b0f4-8ec1f07cd580/O BJ/?metadata=true In case of binary it will return triples instead of the binary resource In case of an container i will get you the RDF (basically ignoring this option)
Also moved some route parameters to query arguments (checksum) in all routes: tx ,checksum and metadata (depending on what is used in each route)
Did also a lot of coding cleanup. Not sure if the Symphony coding standard as base is good enough? Moved the ->abort for non existing resource path in triple store into the middleware.
|
Superseded #131 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So here's the smallest thing I could think of that showcases what I've been trying to describe. It's pretty small, and shows that really all we're trying to do is hack info out of the request and return responses. This is what is meant by 'Thin Controllers'. All the heavy lifting is done elsewhere. In this case, it's Chullo.
As things grow, we can either have a lot of these little guys, or try and manage all of them in a single deployable project.