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.

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

remove frames / values from returned stream data, put into separate route #5

Closed
fjenett opened this issue Apr 21, 2015 · 2 comments
Closed

Comments

@fjenett
Copy link

fjenett commented Apr 21, 2015

to ease heavy traffic it would be better to not include the frames (values) but have them returned through a separate route or additional parameter. for example:

GET streams/<uuid>
--> { meta data only }

GET streams/<uuid>/frames
--> { meta data + actual frames }
@dasantonym
Copy link
Member

absolutely, that is what i am currently implementing to solve PieceMeta/piecemeta-angular-frontend#14

there's actually more options to this... i'd like the api client to be able to

  • load a full stream
  • load only the descriptive data of the stream
  • load only the frame data
  • load quantized data (every nth frame)
  • load a frame range

the last two would require more action on behalf of the api server which is why i'm thinking to move the data storage to hdf5 and throwing out mongodb https://hdfgroup.org/HDF5/
it has native bindings through https://github.com/ryancole/hdf5.node

but for now, those two routes will be quickly implemented.

@dasantonym
Copy link
Member

http://doc.piecemeta.com/#/get-stream-frames
and
http://doc.piecemeta.com/#/get-stream-meta

also, the stream index for a channel does not send frame data anymore:
http://doc.piecemeta.com/#/get-streams-for-channel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants