Yahoo rebuild

[Clippy]

Sound v. interesting.

http://news.bbc.co.uk/1/hi/technology/7366674.stm

NickFitz may know the lowdown.

[NickFitz]

Sound v. interesting.

http://news.bbc.co.uk/1/hi/technology/7366674.stm

NickFitz may know the lowdown.

Some of it

Internally it's known as the Yahoo! Operating System. The basic idea is to modularise all the different services that Y! provides as web services accessible via a consistent set of APIs that can be easily stuck together via HTTP.

So if, for example, you want a site that allows a user to sign up with an existing Y! account and be able to incorporate their flickr photos, their contacts from their Y! Mail address book, their avatar(s), content they've contributed to Y! Answers, their bookmarks from del.icio.us... etc. etc., it's very easy to do - on the back end you're basically using a bunch of HTTP calls to assorted services to bring all that stuff together to be presented in the front end.

There's a lot more to it than this in terms of the APIs that are (or will be) available, and of course there's a lot of infrastructure behind it including important stuff like intelligent caching, otherwise things could become rather slow

If you have a Y! account and you have, over the last few months, been asked to agree to a change in the terms of service to allow them to cache your registration info on a European server, rather than in the mainland US, that was because of a project I worked on which was using the CoreID API to its fullest extent, for the purpose of keeping users informed about their contacts: it was only once a dev team in Europe started using it in anger that the North Americans realised that having all those API calls going back and forth across the Atlantic was rather susceptible to the speed of light and network latency

You could already do most of this stuff via various mashup techniques, but the aim is for consistency across the whole Y! network, which was previously quite disparate in the way the different parts worked. It allows pretty cool stuff to get done a lot quicker.

[MrRobin]

Hmm, don't think I got that email. I did get sent a nice colour changing mug from Y! answers a while back tho.

[Moscow Mule]

Is there any chance they'll drop the "!" ?

[Xenophon]

Is there any chance they'll drop the "!" ?

We can but hope.

[NickFitz]

Is there any chance they'll drop the "!" ?

No, but Microsoft will become "Microsoft!"

[sasguru]

Some of it

Internally it's known as the Yahoo! Operating System. The basic idea is to modularise all the different services that Y! provides as web services accessible via a consistent set of APIs that can be easily stuck together via HTTP.

So if, for example, you want a site that allows a user to sign up with an existing Y! account and be able to incorporate their flickr photos, their contacts from their Y! Mail address book, their avatar(s), content they've contributed to Y! Answers, their bookmarks from del.icio.us... etc. etc., it's very easy to do - on the back end you're basically using a bunch of HTTP calls to assorted services to bring all that stuff together to be presented in the front end.

There's a lot more to it than this in terms of the APIs that are (or will be) available, and of course there's a lot of infrastructure behind it including important stuff like intelligent caching, otherwise things could become rather slow

If you have a Y! account and you have, over the last few months, been asked to agree to a change in the terms of service to allow them to cache your registration info on a European server, rather than in the mainland US, that was because of a project I worked on which was using the CoreID API to its fullest extent, for the purpose of keeping users informed about their contacts: it was only once a dev team in Europe started using it in anger that the North Americans realised that having all those API calls going back and forth across the Atlantic was rather susceptible to the speed of light and network latency

You could already do most of this stuff via various mashup techniques, but the aim is for consistency across the whole Y! network, which was previously quite disparate in the way the different parts worked. It allows pretty cool stuff to get done a lot quicker.

NickFitz is awarded +100 Sasguru nerd points.
(much more valuable than Xeno Geek points, pah!)

[Xenophon]

NickFitz is awarded +100 Sasguru nerd points.
(much more valuable than Xeno Geek points, pah!)

[NickFitz]

NickFitz is awarded +100 Sasguru nerd points.
(much more valuable than Xeno Geek points, pah!)

[HankWangford]

nick sounds like you have a proper job, I'm tired of working for clients who a) dont really give two sh*ts if it takes 100ms or 10 secs, b) will never have enough users to give a sh*t