apptik / jus Goto Github PK

this is handy in RetroProxy where requests could not be automatically added to the queue. Default behavior will be still that requests will be added to the queue automatically.

that produces retry policy for a request

Handle null fragments. square/okhttp@e4dd6cf#diff-a8e006f4a0ae4c4659185aee47a5b7ad
Encode enough to make URI happy. (curly brackers) square/okhttp@080e753#diff-a8e006f4a0ae4c4659185aee47a5b7ad

http://sookocheff.com/post/api/on-choosing-a-hypermedia-format/

normally http stacks can handle all intermediate actions of the http layers involved but since we support caching and auth it makes sense to have light support for redirects 302/307 and 301/308

9.4 HEAD

The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request SHOULD be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext links for validity, accessibility, and recent modification.

The response to a HEAD request MAY be cacheable in the sense that the information contained in the response MAY be used to update a previously cached entity from that resource. If the new field values indicate that the cached entity differs from the current entity (as would be indicated by a change in Content-Length, Content-MD5, ETag or Last-Modified), then the cache MUST treat the cache entry as stale.

for general events in queue actors such as dispatchers, cache, network, stacks ...

when 2 calls happen very fast

http://tools.ietf.org/html/rfc7230#section-6.3.1:
"A user agent MUST NOT automatically retry a request with a non-
idempotent method unless it has some means to know that the request
semantics are actually idempotent, regardless of the method, or some
means to detect that the original request was never applied."

Add tag annotation to retroproxy so requests can be nicely identified

add authenticator factory to a queues so requests can have specific authenticator assigned to them when added

in canUseForInBitmap when no inSampleSize is set

add instead ready to use logger-like callback impl and observers for rx-jus

https://github.com/mikekelly/hal_specification

only the ones that override parseNetworkResponse

when request is placed when offline or cannot be executed for some other reason to be persisted and executed when current status allows this.

trim all header chars where :
c <= '\u001f' || c >= '\u007f'

priority is now obtained from getPriority which needs to be overwritten.
make this as variable with a setter will allow not only easy usage of this but also that RetroProxy to use this function as well.

https://github.com/kevinswiber/siren

http://tools.ietf.org/html/rfc2045#section-5

http://amundsen.com/media-types/collection/

http://www.markus-lanthaler.com/hydra/

transform NetworkRequest before added to the queue and NetworkResponse just after received from the HttpStack