I am currently in the process of choosing a technology/format to expose my API. It seems there are lots of discussion on this topic, but could not find the one for future use. I am planning to use Hydra:
http://www.markus-lanthaler.com/hydra
as it seems to be fully restfull (hypermedia api) but it seems it is not accepted yet (neither HAL is).
when I go to : http://www.markus-lanthaler.com/hydra/api-demo/vocab, I get a json that seems to be what swagger returns.
my questions:
- is Hydra Documentation meant to be sthg like swagger
- could find any tool for it like swagger has.
- I would prefer using Hydra as it seems it has more description on operations... by using json-ld, but it does not seem to be as supported as Hal or swagger is.
-does anyone have experience with hydra
Great that you consider using Hydra. You are right, we do not have extensive tooling yet but that's just a matter of time. In fact, I'm already working on a documentation generator. If you have further questions regarding Hydra, please don't hesitate to post to our mailing list. There are a lot of people on that list that will be happy to help.
Related
I'm working on an app written in Codename One together with the parse4cn1 library, the combination of which is a real pleasure to use. However, I need support for a few things in parse4cn1 that are not implemented, most importantly ACL and was wondering if Chidiebere has any hints on how to do this (e.g. how did you implement parse4cn1 yourself - from scratch or copying the open source Parse SDK for Android)? If I manage to do something of a decent quality I will try to share back. Thanks in advance
I never got around implementing ACLs (it's still on the TODO list). parse4cn1's interface closes resembles the Parse Android SDK interface and I'll like it to stay that way for convenience. In this case, the interface of interest would be the ParseACL which is documented here.
The actual implementation will need to be done via REST API calls.
Things to bear in mind:
We use the Android SDK API simply for defining methods and signatures for the corresponding class in ParseACL but do not use the SDKs for anything can be be done via REST.
By design, any calls requiring the master key will not be supported in parse4cn1 due to security considerations. If really needed, the functionality should be exposed via server-side cloud code.
Pull requests without unit tests for the added functionality or breaking existing tests will be rejected.
See also the Contributions section of the parse4cn1 github repo.
Good luck with your implementation and I hope to see a PR from you soon ;)
It was implemented from a Java port on top of the REST API's here but was later modified to use the SDK's to allow things like push (which are now no longer relevant).
In the past I just contributed pull a request to the project to get the fixes/features I needed. It was really easy to work with and compile.
https://github.com/platanus/angular-restmod seems much clearer to me than restangular but I can't find much info about it - has anyone used it, know of any pitfalls, etc.?
For instance, I can't see support for PATCH for partial updates. Any and all info is welcome.
We are using Angular Restmod in various projects in production and I can tell you it does what it says it does.
Take a look at the issues in Github, there's a lot going on there right now.
I'm trying to understand how to use Json-RPC calls in Google Go that would be used in a Google App Engine app. So far I understand that I somehow should call rpc.Client.Dial, but I don't understand what the "network" and "address" parameters should be. Can anyone provide a sample, working code that demonstrates how to use Json-RPC in Go?
I have already written an answer to your question on the go-nuts group, but for completeness, here it is:
Go's jsonrpc package isn't compatible with GAE yet.
Reference: https://groups.google.com/d/msg/google-appengine-go/uQ0cv0m9j0E/H3VCrFgEWvcJ
It's probably a good idea to read the full thread there, since it describes the limitations on GAE nicely and links to a patched library with lots of workarounds... The issue is already known, but has not been solved yet.
I have created a database using Berkeley DB in C. Now I want to use a libcurl function to send the entries in the database to a server. Can anyone suggest me good examples to read which address somewhat similar scenarios or any other material. I researched a bit and the libcurl homepage has some examples, but I am not able to understand them properly, how to use it in my context. I need examples only for "C" language. thanks in advance.
See the libcurl tutorial for a overview of libcurl, You may also want to look at the easy api reference, as that's what you'll most likely be using
I'm really interested in being able to annotate my data. I am not really sure where to start, so I thought of using Apache Uima with Solr. I'm not sure if I'm no the right path, yet. Anyhow, I'm looking for some good documentation on this component called Solr-Uima
http://code.google.com/p/solr-uima/
Thanks,
J
I have no idea what UIMA is, but when I can't find any docs I read the tests. If the tests are not enough I read the code itself. (sorry if this is a generic answer, but this code doesn't seem to be too difficult to follow, so I really think it's a viable option).
The former project on Google Code has been contributed to Lucene / Solr codebase.
There is a wiki page, but needs to be updated.