This is my first post on the -dev mailing list, and I admit that I
haven't been using Agavi all that long, but long enough to notice a few
areas that could be improved.
I'm toying with some AJAX backend actions, written in Agavi, and have a
few concerns with the way that content-types are handled. At the moment,
I'm manually calling PHP's header() function in my view to set the
content type. If there is a better way of doing this, please advise.
My concern is that if I use text/xml as the content type, and Agavi
raises an exception, my client-side JavaScript doesn't understand this
since it's not XML.
I suggest that Agavi should have some concept of the content-type it is
serving, and render the exception accordingly. This means that we'd have
to come up with a basic XML schema for expressing the information
contained in the normal HTML exception.
This also raises the question of image content-types. For example, I
might want to use JPgraph inside an Agavi controller. While this is not
as important to me as supporting XML-formatted exceptions, it would be
nice if Agavi was able to render a PNG/GIF/JPG exception also, depending
on its content-type.
_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
