Tuesday 07 June 2011 3:22:38 pm
Seems like it's intended, I guess it depends on what the content/type headers say. It gives the user more power to implement it how they see fit. A downside is a lack of support for different types of content. But is it worth it for eZ Systems to implement a bunch of different handlers per content type? Probably not. I found a few references of its use in the kernel as well as the class definition in doxygen. [ezroot]/kernel/setup/steps/ezstep_site_types.php [ezroot]/kernel/shop/classes/exchangeratehandlers/ezecb/ezecbhandler.php I didn't see any issues (open nor resolved) for parseHTTPResponse that pertain to your question either.
Brandon Chambers
[email protected]
blog: http://blog.divdesigns.com
Granite Horizon / http://granitehorizon.com
|