On 12 Apr 2007, at 02:12, Nic James Ferrier wrote:
Mr I Forrester <[EMAIL PROTECTED]> writes:
I did talk to the twitter guys about this issue. I think from there
point of view, they never said twitter was meant to be a real time
system. It just behaved like that from the start.
They're winding you up.
Have you noticed the tricks they're putting in to make you think your
updates are going live?
When you post the post is added to your list on the client side. It's
async-ajaxed to the backend as well. But if you refresh and it hasn't
got back yet it disappears from your list.
Whoops.
I think they know perfectly well how interactive it should be but
they've built it wrong and are now playing catch up.
Nic, sorry, but this is just wrong. The ajax updates are there to
reduce page compute time, not to try and 'trick people' into thinking
that it's 'faster'. They really did intend for it to be a status
update tool, something people would update 2-3 times a day. However
people are using it real time - and a number of bots are posting
super frequently (eg, the beeb feeds).
So yes, it was architected badly in the first place, but this doesn't
mean that they knew what was going to happen....
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/[email protected]/
