PUBLIC MARKS with search handle

Perhaps the biggest win is that Web Intents put your visitors in control — they can select which actions they’d like to perform and which external sites they’d like to handle those actions.

Books need to be a predictable size; they have to be manufactured to a price, stored, transported and displayed. Then they have to fit on home bookshelves. People tend to like books that are easy to read, handle, and store. We generally like and need novels to be certain sizes. If you picked up a diary-sized novel in a series one day and the sequel was the size of a family bible, you'd probably find that annoying. I know many readers won't buy hardcovers and wait for mass market paperback editions simply because the regular size of "MMPBs" fits their bookcase, or is easier to carry around.

So, production editors and typographers do a very clever job of smoothing out that big variation using white space and font sizes to get more words on each page - or fewer. They're so good at doing it that a manuscript of 100,000 words can be made into a book that is identical in overall size to one up to twice the length. Don't believe me? Pick a few books at random, do a word count, and then look at the appearance of the pages. You won't notice it unless you're looking for it.

[...]

Page count doesn't mean a thing. It doesn't tell you how much book you're getting for your money. And, to be brutal, if your evaluation of any book is based on how many words you get rather than the impact it has on you and how well it's written - well, that's just dumb. Sorry, but it is. It's not like a pound of apples for 50 pence being better value than a pound for 75 pence. You're not being short-changed if you get a shorter novel. And left wanting more is not being short-changed. It's what good books are supposed to do.

[...]

So don't get hung up about counting pages. A book is as long as it needs to be to tell the story. Just open it, and enjoy.

Kyoto Tycoon is a lightweight database server with auto expiration mechanism, which is useful to handle cache data and persistent data of various applications. Kyoto Tycoon is also a package of network interface to the DBM called Kyoto Cabinet.

Apple service has been designed to handle high volumes of traffic – it does not use anything like stateless HTTP to waste bandwidth.

JavaScript Execution and Browser Limits and a method which can solve “unresponsive script” alerts using Timer-Based Pseudo-Threading. Today, we’ll look at ways to handle large volumes of data within the browser.

What happens when the user zooms? The Nokia N8 removes the fixed element entirely; and we can all agree that’s not the best possible behaviour. But what should happen? I have no clue. Browsers can’t handle the situation, and the spec is silent.

Nov 27, 2010

karl said...

You said: "URIs have become part of the furniture of the real world, like corporate graffiti tags. I'm typing this on a tube train and every poster at this end of the carriage features a URI in some shape."The metaphor is a little bit off. Basically yes you are right in the physical world (everything is real, the difference is more digital-physical), things change too. The poster in the carriage is content (aka the representation served to you), but this is not the URI. The URI in the carriage in this case is the pointer which led to this poster. It could be for example "carriage XZ345-window AXV" This is the identifier, the URI. The content can change it is no issue. Now the URI helps you to designate and draws an expectation, at this URI, I'm used to read this or that. Example in the physical world. At this address, 123 Smith Street, etc. (URI = identifier), there is a shop (representation) which sells bread. Maybe one day the shop will be replaced by a fisher place and you break the expectation of the usual person coming here. You break URIs when you do not handle it anymore. Exemple an urban architect redesign the city, and the street completely disappears, where one day the street was here, the next year no more than a big factory on what was one day a street. The important is not that the street disappeared, but that the name of the street disappeared. The History books of the city or the streets around could display a 410 Gone (Here was Smith Street).

D3.js is a small, free JavaScript library for manipulating HTML documents based on data. D3 can help you quickly visualize your data as HTML or SVG, handle interactivity, and incorporate rich animations into your pages.

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/