Cookies were created because HTTP as a protocol can't maintain 'state'. This
was both a good thing - because it allows the Web to simply drop the connection
once it has passed the requested Web page - and a bad thing, because sometimes
you need to do things in sessions, or even across sessions,
At 4:17 PM +1000 26/8/15, Frank O'Connor wrote:
Cookies were created because HTTP as a protocol can't maintain 'state'. This
was both a good thing - because it allows the Web to simply drop the
connection once it has passed the requested Web page - and a bad thing,
because sometimes you need to
Yeah,
Nowadays there are any number of other ways to maintain state, carry little
numbers like user preferences across sessions (server side tech), or even
validate transaction processes in sessions (using server side JavaScript,
client-server JAVA, client JavaScript for data and process
On 2015/Aug/26, at 4:17 PM, Frank O'Connor francisoconn...@bigpond.com
wrote:
Cookies were created because HTTP as a protocol can't maintain 'state'. This
was both a good thing - because it allows the Web to simply drop the
connection once it has passed the requested Web page - and a bad
Isn't that just a war of business models?
Free range advertising v walled garden consumer?
I do not see any relative privacy gains from being internal to a walled
garden?
Do apple allow their consumers to sift or block the privacy intrusions of
their own iApps and advertising?
It doesn't look like
