| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | "Keith C(dot) Perry" <netadmin(at)vcsn(dot)com> |
| Cc: | Chris Travers <chris(at)travelamericas(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: cryptography, was Drawbacks of using BYTEA for PK? |
| Date: | 2004-01-13 21:36:26 |
| Message-ID: | 877jzvcyzp.fsf@stark.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Keith C. Perry" <netadmin(at)vcsn(dot)com> writes:
> Additionally, I almost always use POST methods instead of GET
> (I hate exposing application logic that way).
Well this is pretty far afield from postgres. But I hope you're not using POST
for idempotent operations like search or record lookups. I hate it when I'm on
a site and i can't bookmark pages usefully or use the back button or open
pages in new windows etc.
POST is ideally only used for non idempotent operations like updates, deletes,
etc. Things that you wouldn't want to be repeated when the user hits reload,
and wouldn't want repeated every time a user revisits a bookmark.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Bowden | 2004-01-13 21:38:02 | serverless postgresql |
| Previous Message | netadmin | 2004-01-13 21:13:28 | Re: Best practice? Web application: single PostgreSQL |