On Wed Apr 18, 2007 at 08:38:30PM +0200, Jonas Pfenniger wrote:
> 2007/4/18, Thomas Lockney <[EMAIL PROTECTED]>:
> > On 4/18/07, Jonas Pfenniger <[EMAIL PROTECTED]> wrote:
> > > Hi Carmen,
> > >
> > > to avoid patching Camping, I suggest you look into overriding the
> > > "service" method for the t
2007/4/18, Thomas Lockney <[EMAIL PROTECTED]>:
> On 4/18/07, Jonas Pfenniger <[EMAIL PROTECTED]> wrote:
> > Hi Carmen,
> >
> > to avoid patching Camping, I suggest you look into overriding the
> > "service" method for the target controllers. You can do this in your
> > main application module or by
> controllers whether the data comes in from regular requests or as JSON data.
> Granted, that could still be done in the controllers, but it does end up
> being a bit less elegant.
the main idea is always get @input in the controller regardless of the format -
currently it unnecessarily parses t
On 4/18/07, Jonas Pfenniger <[EMAIL PROTECTED]> wrote:
Hi Carmen,
to avoid patching Camping, I suggest you look into overriding the
"service" method for the target controllers. You can do this in your
main application module or by including a custom module in your
controllers, as you prefer. Le
2007/4/18, carmen <[EMAIL PROTECTED]>:
> what is the cleanest way to do something for every request of a particular
> type (Verb, and Content-Type header)? i'm trying to figure out if shipping a
> custom camping.rb is avoidable, and if, how i should structure a patch
>
>
> my app http://whats-you
what is the cleanest way to do something for every request of a particular type
(Verb, and Content-Type header)? i'm trying to figure out if shipping a custom
camping.rb is avoidable, and if, how i should structure a patch
my app http://whats-your.name/yard/ uses exclusively JSON based messagin
6 matches
Mail list logo
