+1 For response model. First step might be to expand the http package, because that's where abstract/base models should be part of.
Am Montag, 23. Februar 2015 10:42:45 UTC+1 schrieb Andrew Eddie:On 23 February 2015 at 08:01, Michael Babker <michael... AT gmail.com> wrote:
> In our social packages, we only return a formatted response body from our
> methods, which makes the rest of the response data inaccessible. In the
> case of GitHub, this makes it difficult to access the response headers to
> check the different data they send back with requests (such as pagination
> links for list APIs or rate limits). So we need to make an adjustment to
> those APIs IMO to give access to the full response data. Either by storing
> the last response as an accessible API point or adjusting all of our
> endpoints to return the full response (including the formatted body).
I'd probably return either a response model (something with functions)
or a response entity (something with just properties). The model is
probably better as you can define an interface.
You definitely need the ability to inspect headers.
Framework source code: https://github.com/joomla-framework
Visit http://developer.joomla.org for more information about developing with Joomla!
You received this message because you are subscribed to the Google Groups "Joomla! Framework Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-framework+unsubscribe AT googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-dev-framework.