Hi Nicolas,
For now, let me just quickly respond to your question regarding
__debugInfo():
The RFC is also missing whether __debugInfo returns raw or non-raw
> components. Then, I'm wondering if we need this per-component break for
> debugging at all? It might be less confusing (on this encoding aspect) to
> dump basically what __serialize() returns (under another key than __uri of
> course).
> This would also close the avenue of calling __debugInfo() directly (at the
> cost of making it possibly harder to move away from parse_url(), but I
> don't think we need to make this simpler - getting familiar with the new
> API before would be required and welcome actually.)
>
I mostly have already answered this in my latest message to Ignace: yes, I
think it makes sense to provide a clear picture about the anatomy of an URL
in some cases. The method uses raw component values in order not to skew
the original data.
Máté