-
Notifications
You must be signed in to change notification settings - Fork 16
Customize api for paging #31
Comments
thanks @maxcda101 We can offer to help but you would need to be willing/able to "sponsor" this work at the moment, its not a priority for us. If you prefer to review the related code/documentation for this area and suggest an approach, we may be able to guide you as to a solution you can craft yourself and then submit related pull request. Hope that helps? |
thanks Tony On this issue I have resolved already. Quan Nguyen from ThinkLabs-VN |
thanks Quan Nguyen
You say resolved?
Is that something you're submitting a pull request on /need to discuss
further here?
re " customize the api retrieve data from ethercis" .. assume you mean on
the Qewd-Ripple side?
If so what changes do you suggest to the codebase?
thanks
Tony
…On 26 June 2017 at 08:07, Nguyen Quan ***@***.***> wrote:
thanks Tony
On this issue I have resolved already.
But you should customize the api retrieve data from ethercis, when the
data up very large will cause the system to slow down.
Quan Nguyen from ThinkLabs-VN
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA5X3Lk963eR9OLNrv8MZc442fXeZAMLks5sH1iXgaJpZM4Nz24Q>
.
|
Hi Ripple Team,
I have a problem, that I have a medical device to automatically push vitalsigns information up RippleOsi, so a lot of data is posted up.
When I call api
/api/patients/:idpatient/vitalsigns
to get the data, the data returns very slowly and many records.So I want to customize the api to reduce load and paging, for example
/api/patients/:idpatient/vitalsigns?start=5&limit=10
Then the result returned 10 records and started from order = 5, but I can not do it.
Also, I also want to customize for the other api: patients, procedures, events ....
Can the Ripple Team be customized to help me or have any other solution?
Thanks and Best Regards.
Quan Nguyen from ThinkLabs-VN
The text was updated successfully, but these errors were encountered: