PUBLIC MARKS with search agent

But I’ve long had a similar question about NetNewsWire. Back in 2002 and 2003, when NetNewsWire would read a feed, it would send the URL of NetNewsWire’s product page as the referer. That was wrong. (It’s also what other readers did, so I justified it as the then-current best practices.) It wasn’t a privacy violation — it wasn’t terribly wrong — but it was still wrong because it was misusing the referer. (The user-agent is where that info was supposed to go.)

a strict subset of the full HTML5 specification that omits user-agent (UA) implementation details. It is targeted toward Web authors and others who are not UA implementors and who want a view of the HTML specification that focuses more precisely on details relevant to using the HTML language to create Web documents and Web applications.

L’échec doit avoir sa place pour que l’architecture agisse comme agent de changement culturel. » -Robert Somol, juillet 2011

Oct 04, 2010

karlpro said...

HTTP gives you a way to handle the right user (agent) interaction. In the discussion there is a missing piece above. What is the URI? The HTTP code will give information about a URI and its evolution in time. For a user agent, is it a fixed one or temporary one? I'm surprised you didn't use a 307 Temporary Redirect. The information accessible at this URI is not accessible anymore, you can send the client to another URI with with an Expire field, with the information that the client has reached its limits and should retry the original URI in xxxx minutes. What is happening on the server side, machine limits, disks, etc. is *not* important and not part of the exchange of messages. Think about what is useful for going to the next meaningful interactions in terms of messaging (for a human or a software).Note also that HTTP WG is at work to define HTTPbis and it is the right time to have contributions of people who have real implementations issues. I would encourage you to send an email to the HTTP Working Group at ietf-http-wg@w3.org with the link to this blog post and an introduction.The draft documents are available at http://tools.ietf.org/wg/httpbis/

The ProtoFluid App

* Facilitates web app testing on various screen sizes, orientations and browsers.

* Lets you design for CSS3 compliant (mobile) browsers using Media Queries.

* Particularly suited to the early development of fluid layout based web applications.

* Use all your favourite web browser development tools (Firebug etc.)

* This approach is particularly relevant considering the upcoming tablet tsunami.

* Encourages modern design flexibility. No browser sniffing or user agent strings here!

The ProtoFluid App

* Facilitates web app testing on various screen sizes, orientations and browsers.

* Lets you design for CSS3 compliant (mobile) browsers using Media Queries.

* Particularly suited to the early development of fluid layout based web applications.

* Use all your favourite web browser development tools (Firebug etc.)

* This approach is particularly relevant considering the upcoming tablet tsunami.

* Encourages modern design flexibility. No browser sniffing or user agent strings here!