This is definitely a problem.
This is definitely a problem. I work with an existing API and am building a mobile client based around it, and while there's limited support for selecting which fields you bring down, it doesn't work for nested object. This results in a bloated response, which on mobile is a real problem for responsiveness and data costs. We considered building a proxy which would form responses tailored for the mobile client, but that felt like a hack. Mind you, so does Google's partial response solution. Maybe some services could allow you to build your own response, creating a custom version of an API just for yourself?
Posted by colinramsay on May 6, 2014, 11:33 AM
Tags
Related issues
- I hate that folks recommend random extensions.
- This is my biggest problem with agents, they constantly defensively code for cases that have no chance of happening and in most cases a p...
- I wish there was something like LEAN for biology.
- The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
- I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
- I hate that I'm in deep enough to know what you mean.
Raise real-world problems, find people facing the same issue, and discuss solutions.9,500 issues0 comments
reliability (Other)
I hate that folks recommend random extensions.
NewThis is my biggest problem with agents, they constantly defensively code for cases that have no chance of happening and in most cases a p...
I wish there was something like LEAN for biology.
The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
I hate that I'm in deep enough to know what you mean.
The biggest problem with “AI” is that big corps are shoving it down our throats.
in the middel of a coding session with 5.6 sol.
This is definitely a problem.
This is definitely a problem. I work with an existing API and am building a mobile client based around it, and while there's limited support for selecting which fields you bring down, it doesn't work for nested object. This results in a bloated response, which on mobile is a real problem for responsiveness and data costs. We considered building a proxy which would form responses tailored for the mobile client, but that felt like a hack. Mind you, so does Google's partial response solution. Maybe some services could allow you to build your own response, creating a custom version of an API just for yourself?
Comments (0)
No comments yet. Start the discussion.