Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #81840
| From | Gregory Ewing <greg.ewing@canterbury.ac.nz> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Cherrypy - prevent browser "prefetch"? |
| Date | 2014-12-03 19:17 +1300 |
| Message-ID | <ce7o7pFgph2U1@mid.individual.net> (permalink) |
| References | <6B74D6DD-A597-4BCF-8586-D0A56C9CDB77@ravnalaska.net> <1417527181.1832828.197804893.3AA95580@webmail.messagingengine.com> <mailman.16494.1417536013.18130.python-list@python.org> |
Israel Brewster wrote: > Primary because they aren’t forms, they are links. And links are, by > definition, GET’s. That said, as I mentioned in earlier replies, if using a > form for a simple link is the Right Way to do things like this, then I can > change it. I'd look at it another way and say that an action with side effects shouldn't appear as a simple link to the user. Links are for requesting information; buttons are for triggering actions. -- Greg
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Cherrypy - prevent browser "prefetch"? Israel Brewster <israel@ravnalaska.net> - 2014-12-02 06:59 -0900
Re: Cherrypy - prevent browser "prefetch"? Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-12-03 19:17 +1300
Re: Cherrypy - prevent browser "prefetch"? Israel Brewster <israel@ravnalaska.net> - 2014-12-03 10:06 -0900
csiph-web