Christian Szardenings wrote:
why do you recommend that? Is deleting by GET some kind of security
issue? Or is it just a 'usability' improvement (e.g. don't delete
'again' when user hits the back button) ?
I typically POST to /articles/delete, with id=>1234 as post data.
This gets you to the
Hi,
> Well, for one, if your site gets indexed, you don't want a spider going
> through and deleting records...
this is the way I solve this.
/user/1/delete => shows the deletion page for user 1 (are you sure?)
/user/dodelete => deletes the user that is passed by POST data
Jm2c.
Best Regar
<[EMAIL PROTECTED]>
To:
Sent: Wednesday, December 06, 2006 7:35 AM
Subject: Re: [fw-general] Understanding Web MVC Applications / Controller
Organization
Hi Matthew,
I would highly encourage you to delete via POST, not GET--regardless of
user permissions.
why do you recommend that? Is d
-- Christian Szardenings <[EMAIL PROTECTED]> wrote
(on Wednesday, 06 December 2006, 04:35 PM +0100):
> > I would highly encourage you to delete via POST, not GET--regardless of
> > user permissions.
>
> why do you recommend that? Is deleting by GET some kind of security
> issue? Or is it just a '
Hi Matthew,
I would highly encourage you to delete via POST, not GET--regardless of
user permissions.
why do you recommend that? Is deleting by GET some kind of security
issue? Or is it just a 'usability' improvement (e.g. don't delete
'again' when user hits the back button) ?
Greeting
Ralph,
> What if I wanted to limit the ability to Creating/Updating/Deleting to a
> certain group of people (Access Control / admin type) and I wanted
> funnel this through a super-controller. Is that possible, is this a
> correct method? For example:
>
> I want to disallow direct controllers li
Matthew Ratzloff wrote:
Controllers
---
These classes have indexAction(), createAction(), updateAction(),
viewAction(), saveAction(), deleteAction(), etc. Some people prefer these
names to be plural.
- StudentController
- ProfessorController
- ClassController
- Organization
Hi Ralph,
It depends on what sort of information you're capturing for each member
type (students, professors, etc.). Assuming the two do not have much
overlap, and going on just the information you provided, I might do the
following:
Domain
---
These classes handle things lik
Assuming there is a ZF 1.0 and I am a developer totally onboard with the
MVC mantra, where can I go to understand how to start THINKING in the
right frame of mind about my project? What I mean is, in the framework
world, the design patterns library explains to us how to speak about
problems an
