Re: [GSOC 2017] Python-HYDRA - Phase 1 Report

Hello everyone,

Hope all of you are doing well. I'm Chris Andrew, one of the students
working on the Python Hydra project as part of the Google Summer of Code.

As mentioned, we have been able to setup a general server side application.
I have a few things I would like to know more about regarding Hydra and how
the server should work:

   1. Are there any more uses for a Collection other than showing available
   instances?
   2. What is the right way to create a new instance, should it be a POST
   to “/api/ClassCollection” URL or the “/api/Class/<intended_id>” URL.
   3. Is the DB Model mentioned in the report good enough, or is there any
   other way we can create a more efficient storage system?
   4. What can be a good use case for a Hydra enabled server and how can a
   generic client be used for it?
   5. Is Markus Lanthaler's Hydra Console a good starting point for a
   generic client application?
   6. How would you define argument based Operations that are not dependant
   on a single HydraClass in Hydra, for example, I have an operation called
   “Join”, that will take any two instances as arguments and then joins the
   attributes of both the instances into a single new instance? How will such
   operations be used/called?

These are some of the things I had in mind. I hope you guys can help me
address a few of them, so that I can get a better idea about Hydra. I've
also added them to the document at: https://tinyurl.com/y8784gtn for
convenience.

All in all, Hydra is a wonderful initiative and it's been fun learning and
being part of this project. I hope to get some valuable ideas and feedbacks
from all of you at HydraCG.

Regards,


On Sun, Jun 25, 2017 at 11:46 PM Lorenzo Moriondo <tunedconsulting@gmail.com>
wrote:

> Hi all,
>
> After the first month of development
> ​for​
>  Python-HYDRA
> ​project during ​
> Google Summer Of Code
> ​2017 ​
> program, we have prepared a report about actual achievements and future
> goals, we would like to have as much feedback as possible
> ​ based on the material linked on this mail​
> .
>
> The students that are working hard are Chris and Akshay, they are both
> cc’ed. I have been designing and following the development as a mentor.
>
> Briefly, we managed to develop a pretty general server-side framework and
> we will jump into developing a client and a demo-infrastructure that will
> experiment usage of the API by simulating multi-machines interactions.
> You can check :
> * the code at https://github.com/HTTP-APIs/hydrus
> * the wiki at https://github.com/HTTP-APIs/hydrus/wiki that states design
> principles for the demo-API and
> ​how to ​
> set up the demo-application.
> * a running server can be tested via Markus’ client at
> http://www.markus-lanthaler.com/hydra/console/?url=http://54.169.232.177:8080/api
>
> ​S​
> tudents performed well and you can find the report at
> https://tinyurl.com/y8784gtn
> This mail will be followed by students’ mails in which they will introduce
> themselves and tell you about their experience with
> ​the Specs​
> , asking their questions.
> ​ ​
> I am sure you will be happy to provide feedback about the document and the
> code
> ​ by replying on the list and/or adding comments/issues on Github..​
>
> Best,
>
> --
> ¤ acM ¤
> Lorenzo
> Moriondo
> @lorenzogotuned
> https://stackoverflow.com/cv/lorenzomoriondo
> https://www.linkedin.com/in/lorenzomoriondo
> https://github.com/Mec-iS
> https://profiles.udacity.com/u/lorenzomoriondo
>



  <https://mailtrack.io/> Sent with Mailtrack
<https://mailtrack.io/install?source=signature&lang=en&referral=chris..g14@iiits.in&idSignature=22>
-- 
----------------------------------------
Chris Andrew
Indian Institute of Information Technology
Sri City - 517541
Chittoor District, A.P., India

Received on Sunday, 25 June 2017 18:42:46 UTC