Actually, it's not a pure REST API since we need server pushes. This can either be realized over Websockets or Server Sent Events.

One implementation supporting our requirements would be Jersey.

I started working on the webservice API on top of Hive2Hive. I am willing to do that in Jersey (unless you'd recommend something else). I will update you throughout if I have any issues.

@harkous Did you make some progress with the REST API? What's the current status?

Hi Nico,
Unfortunately, not. Graspeo project has significantly pivoted since the
last discussion. The p2p part became outside the main project plan and we
had to allocate the resources on another part. I'm very sorry for that.

On 17:21, Wed, Nov 19, 2014 Nico Rutishauser notifications@github.com
wrote:

@harkous https://github.com/harkous Did you make some progress with the
REST API? What's the current status?

Reply to this email directly or view it on GitHub
#68 (comment).

Hello,
I would like to contribute to this issue. @nicoruti Could you please elaborate on the use cases of the REST API

Hi @raman-hike
Thanks for your interest in Hive2Hive.

The goal of a REST-Interface is to decouple a possible UI from the Hive2Hive core. Currently it's only possible to write a Java Client for Hive2Hive. With a REST-Interface, we could run Hive2Hive as a daemon, enabling any application to use it (like a password-manager, notepad, etc.), that is not necessarily written in Java.

Basic functionality would be like registering, logging in, synchronizing files / folders, etc. Unfortunately, the core is not stateless, thus only one user can be logged in at a time.

That's basically the use case for a REST API. Best to implement would perhaps be in a separate module (dependent from the core module).

@nicoruti Thanks. I am independently starting this project for learning purpose. I would appreciate your help if required in future