Plugins planned

[joelwurtz]

plugins planned (new or migrate from Ivory):

• Authentication (replaces BasicAuth by @sagikazarmark)
• Cookie (Journal interface #35, migrate)
• History (migrate)
• Logger (migrate)
• Redirect (migrate)
• Retry (migrate)
• Tape Recorder (PHP-VCR like by @jeromegamez, see tape recorder php-vcr style #4)
• Stopwatch (migrate)
• Convert error responses to exceptions (throw exception when status is 4xx / 5xx)
• Base URI (to complete incomplete requests, see also Dependencies #37)
• Validator (validate http request based on protocol (1.0 / 1.1)
• Sanitizer (add http request headers based on available informations, like Host header, Content-Length header, ...)
• Encoding : Deflate, Chunk, ... (Add header to request to say that we support compression, and decorate stream for deflate / chunk if needed)
• Cache (integration with doctrine / cache, psr 6 ? )

[jeromegamez]

Are you okay with me implementing the Tape Recorder part :)? Unless someone else is already at it, of course!

[joelwurtz]

No problem go ahead :)

[sagikazarmark]

@jeromegamez it's good to see you here. 😄

No problem at all, it is your baby anyway.

I was looking at VCR. Do you think there is a possibility to join forces with them? Honestly, I never used these tools too much, just played with them. However, if they are the same, why couldn't we team up with them?

I don't insist on it, I leave this to you, but it would be good to investigate what the possibilities are.

[sagikazarmark]

What's the difference between history and logger?

[dbu]

@jeromegamez awesome! i created #4 to discuss this in its own thread.

[joelwurtz]

What's the difference between history and logger?

Logger log request / response / exception to a psr/log implementation
History keep trace of http calls (request response couple) in a journal

The real distinction comes from the "couple" thing, in logger plugin there a just some events which may or may be not related, in history the trace is always with the couple

[sagikazarmark]

I see. Where is history data kept?

[joelwurtz]

The default implementation from ivory http adapter kept data in memory (with a variable), see https://github.com/egeloen/ivory-http-adapter/blob/master/src/Event/History/Journal.php

[dbu]

so the history one would be a meta plugin for other tools (like a symfony toolbar integration) to extract what happened during this request?

[joelwurtz]

so the history one would be a meta plugin for other tools (like a symfony toolbar integration) to extract what happened during this request?

Like a data collector thing yes

[sagikazarmark]

That sounds good. @dbu can it somehow be added to the HttplugBundle?

[dbu]

yes, HttplugBundle would be the right place for integrating the history plugin with the symfony toolbar

[joelwurtz]

Updated the list :

Compression and Chunk should be in one plugin (Encoding)
Add Cache Plugin (i have see many libraries using cache system to avoid doing to many calls to an api endpoint)

[sagikazarmark]

Cache is something that is experimental even in guzzle, would be nice to have. Not sure though whether we need cache if we have VCR or not.

[joelwurtz]

I think they all depend on a mutual dependancy like the Formatter / Normalizer thing (which can also be used in the Log plugin), so we can serialize a http request in another format. But despite from that workflow and usage is not the same.