Jaldhar H. Vyas wrote:
> As I said to him when we had our IRC conversation that day, the main bit
> that is missing is dispatch based on MIME types.
Well, it lacks being able to dispatch on HTTP request method too. I'm confused
about the MIME types bit though. I don't seem to remember how they are
associated with REST.
> Do you think I should not continue with my module? Although it is not
> as featureful as C::A::Dispatch it is more lightweight and the features
> are "good enough" for many applications I should think. Also mine is a
> plugin while C::A::Dispatch can only be used as a base class right?
C::A::Dispatch is neither a plugin nor an application base class. It's a wrapper
that sits outside of your C::A modules and acts as a gatekeeper. You can
subclass it to further refine the behavior though.
>> I like the way Catalyst::Action::REST implements its REST
>> functionality personally.
>
> You mean with attributes? Rhesa suggested this also. My only concern
> is that it would slow things down a bit. I am going to try and
> implement this just to see if the performance hit is noticable or not.
For me it's not a performance issue. I prefer to have all my dispatching code in
one place. That way if there's some problem, I only have 1 place to look, rather
then looking over every module and every run mode.
--
Michael Peters
Developer
Plus Three, LP
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.