[email protected] wrote:
--> So, tell me, would you like to allow people to bookmark transaction
ID numbers or attributes which are not permanent (ie will last until a
transaction is done)?
Why would a user try to bookmark such a page? It doesn't make sense.
What harm would it do if they did anyway? At worst, they should get an
"Unrecognized transaction" error.
More usefully, a log of the transaction could be supplied.
Fact is, guidelines are there for best practices but rules are meant to
be bent when we encounter different problems/scenarios. Another factor
is the business rules. If they business doesn't want its subscribers
(for what ever business acumen/reason
Such as?
or perhaps to discount future
maintenance of having to put in redirects when they decommission or
rename certain URIs) to have a bookmark for them to achieve certain
things (ie. look at their electricity bills), then POST would be the
better pick.
Limiting the side effects of laziness and bad practices with other bad
practices ... well, that's an interesting argument, I'll give you that.
Also, when POST is used , the URL on the url address bar of the browser
remains clean without the extra params.
URLs should be designed to be useful, not pretty (with the possible
exception of those to be printed out on promotional materials - which
the ones under discussion wouldn't be).
--
David Dorward
http://dorward.me.uk/
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
