On Jan 19, 2008, at 11:45 PM, Jonathan Rockway wrote:
Someone should submit a patch to make debug settable in the Catalyst
configuration (and off by default). Then you can doc-patch that.
I was actually wishing for this last week but don't have the tuits.
Maybe everyone (well, you core folk)
Shouldn't debug be *off* by default, in any case??
Worst case scenario, you should have to turn it *on* in each page you
want debugging information - not turn debugging *off* in each page you
don't want debugging information.
On Jan 20, 2008 12:36 PM, Ashley [EMAIL PROTECTED] wrote:
On Jan 19,
I'm having difficulty using a foreach loop to read through a file and
call a form to edit the data read and put it in the data base. The for
loop executes but the form is only called on the last data item. I'm
sure there's something I'm missing regarding flow control. I've tried it
two
I know this has been discussed already - but I can't find it in the archives.
What I conjured is:
/class/search
/class/id//view
/class/id//update
/class/create
Update and create use really the same logic and templates - so I just
forward to a create_or_update action from them.
What are
Zbigniew Lukasiak wrote on 1/20/08 1:56 PM:
I know this has been discussed already - but I can't find it in the archives.
What I conjured is:
/class/search
/class/id//view
/class/id//update
/class/create
Update and create use really the same logic and templates - so I just
forward
At 01:56 PM 1/20/2008, Zbigniew Lukasiak wrote:
I know this has been discussed already - but I can't find it in the archives.
What I conjured is:
/class/search
/class/id//view
/class/id//update
/class/create
Update and create use really the same logic and templates - so I just
forward
On Jan 20, 2008, at 1:33 PM, Thomas L. Shinnick wrote:
At 01:56 PM 1/20/2008, Zbigniew Lukasiak wrote:
/class/search
/class/id//view
/class/id//update
/class/create
spew register=pedant
One important topic in the book is that people mix 'verbs' into
their URIs when they shouldn't,
One important topic in the book is that people mix 'verbs' into their URIs
when they shouldn't, or at least when they don't _have_ to. Using the
book's concepts your URIs would become
1) GET/class?pattern=breadbox
2) GET/class/id/
3) PUT/class/id/
4) POST
Dave Rolsky wrote:
On Sun, 20 Jan 2008, Thomas L. Shinnick wrote:
They specifically allow that when PUT is not available or
impracticable (clients, firewalls, and proxies can get in the way),
you could 'overload' POST by, for example, adding a query parameter
_method=PUT to pass-thru the
On Sun, 20 Jan 2008, Thomas L. Shinnick wrote:
They specifically allow that when PUT is not available or impracticable
(clients, firewalls, and proxies can get in the way), you could 'overload'
POST by, for example, adding a query parameter _method=PUT to pass-thru the
real request method.
At 04:06 PM 1/20/2008, =?KOI8-R?B?88XSx8XKIO3B0tTZzs/X?= wrote:
One important topic in the book is that
people mix 'verbs' into their URIs
when they shouldn't, or at least when they don't _have_ to. Using the
book's concepts your URIs would become
1) GET/class?pattern=breadbox
2)
On Mon, Jan 21, 2008 at 01:06:25AM +0300, Сергей Мартынов wrote:
But is the /id/ part of url required? In most cases class would have
only one primary identifier, so we can shrink it to GET /class/ -
can't we?
In this case, we could, but often the identifier for a thing is a
character
On Sun, 20 Jan 2008, Ashley wrote:
Clipped a bunch. This is great food for thought. I am missing in this scheme
how you would know to serve the form for updating. That seems to be the real
point of /class/id//update. I suppose that should be /class/id//edit
instead and it would, if it
At 04:11 PM 1/20/2008, Ashley wrote:
On Jan 20, 2008, at 1:33 PM, Thomas L. Shinnick wrote:
At 01:56 PM 1/20/2008, Zbigniew Lukasiak wrote:
/class/search
/class/id//view
/class/id//update
/class/create
spew register=pedant
One important topic in the book is that people mix 'verbs'
* Peter Karman [EMAIL PROTECTED] [2008-01-20 22:10]:
there's no checking of HTTP method at all.
Yikes!!
img src=http://example.org/foo/id/42/delete;
That API is intentionally RESTish
It’s not REST if it ignores the uniform interface – it’s RPCish.
URI design is completely orthogonal to
Aristotle Pagaltzis wrote on 1/20/08 7:36 PM:
* Peter Karman [EMAIL PROTECTED] [2008-01-20 22:10]:
there's no checking of HTTP method at all.
Yikes!!
img src=http://example.org/foo/id/42/delete;
That API is intentionally RESTish
It’s not REST if it ignores the uniform interface – it’s
On Mon, 2008-01-21 at 04:00 +, Matt S Trout wrote:
On Sun, Jan 20, 2008 at 10:36:41AM -0800, Ashley wrote:
On Jan 19, 2008, at 11:45 PM, Jonathan Rockway wrote:
Someone should submit a patch to make debug settable in the Catalyst
configuration (and off by default). Then you can
On Sun, Jan 13, 2008 at 09:27:55PM -0800, Robert Krimen wrote:
Catalyst::Plugin::Assets
http://search.cpan.org/~rkrimen/Catalyst-Plugin-Assets-0.012/
You seem to be using an 'assets' config key; please change this to
'Plugin::Assets' and deprecate the old one. We're currently moving the 'core'
On Sun, Jan 20, 2008 at 10:36:41AM -0800, Ashley wrote:
On Jan 19, 2008, at 11:45 PM, Jonathan Rockway wrote:
Someone should submit a patch to make debug settable in the Catalyst
configuration (and off by default). Then you can doc-patch that.
I was actually wishing for this last week but
On Jan 20, 2008 10:33 PM, Thomas L. Shinnick [EMAIL PROTECTED] wrote:
At 01:56 PM 1/20/2008, Zbigniew Lukasiak wrote:
I know this has been discussed already - but I can't find it in the
archives.
What I conjured is:
/class/search
/class/id//view
/class/id//update
On Sun, 2008-01-20 at 23:58 -0600, Dave Rolsky wrote:
On Mon, 21 Jan 2008, Aristotle Pagaltzis wrote:
The part where web browsers really do suck – and I really mean
suck utterly terribly – is HTTP Auth, which makes you have to…
well, you don’t quite have to violate REST constraints, but
21 matches
Mail list logo
