Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Basic RESTful API #5

Closed
rufuspollock opened this issue Nov 20, 2011 · 4 comments
Closed

Basic RESTful API #5

rufuspollock opened this issue Nov 20, 2011 · 4 comments
Assignees
@teleyinex
Labels
API priority.high
Milestone
v1.0

Comments

@rufuspollock
Copy link
Contributor

rufuspollock added a commit that referenced this issue Nov 20, 2011
@rufuspollock
[api][m]: (refs #5) start on RESTful API (GET for Project is working).
49be0af
rufuspollock added a commit that referenced this issue Nov 20, 2011
@rufuspollock
[api][m]: (refs #5) POST for project / app now working (plus a proper…
6521801 
… test!).
rufuspollock added a commit that referenced this issue Nov 20, 2011
@rufuspollock
[api][s]: (refs #5) use generified API setup to add API support for T…
a9dbce7 
…ask, TaskRun.
@rufuspollock rufuspollock mentioned this issue Nov 22, 2011
Closed
@nigini
Copy link
Contributor

nigini commented Dec 16, 2011

I thought about working at the API... It would be nice to document how it should be... for example:

  1. registered user asks for a API key (it should have a page to request and see his keys)
  2. API key == UserApplicantion key (OneToOne relation)?
  3. Are there any pattern to generate this? I would like to study about!
  4. each request needs to send the app-key so it can be processed!
  5. it kind of requires a HTTPS request, right? (sure I've seen big sites using HTTP with keys, but...)
    Is it like this? Maybe a new wiki (page/page-session) having this would be nice!

@rufuspollock
Copy link
Contributor Author

Remaing is PUT and DELETE. Will do these and then integrate auth and authz. Auth is #20.

@teleyinex
Copy link
Member

Fine! I think I can try. For the moment I leave the issue open to everyone!

@ghost ghost assigned teleyinex Jan 25, 2012
@rufuspollock
Copy link
Contributor Author

@teleyinex Reassigning to you :-)

teleyinex added a commit that referenced this issue Jan 27, 2012
@teleyinex
FlickrPerson updated for the new DB. Closes #37 Refs #24
ef36d2f 
The new DB model #24 included several changes to PyBossa. Basically, the
removal of the Batches table, and some new fields in some tables
(check the model.py for further details).

The FlickrPerson application finally saves the state of the tasks, so
this new version only presents un-completed task to users. This is
done via the API #5.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@teleyinex teleyinex

Labels
API priority.high
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
3 participants
@teleyinex @nigini @rufuspollock