Featured Post
These days, I mostly post my tech musings on Linkedin. https://www.linkedin.com/in/seanmcgrath/
Wednesday, April 23, 2003
Blog Peeping
This is so cool. Sit back and watch the world blog its way around the clock. Now you know you simply must get those geotags and that RSS autodiscovery machinery into your blog.
Web Services Patents Fun and Games
One Charlie Northrup holds a patent for what are now known as Web Services. Stop giggling there at the back!
Python metaclasses
Had your caffeine? Blood sugar levels okay? If so, you might like to tackle Python metaclasses. If not, don't go there. Your brain will ooze out of your ears and drip to the floor.
Tuesday, April 22, 2003
Blogging and lurking
Something interesting is happening to the concept of a "forum" on the Web. Blogs are changing the way debate is conducted electronically. Here is an ITWorld piece about the subject. Blogging and lurking.
Monday, April 21, 2003
Temporal decoupling
Clay Shirky writes:
It also arguably has caused technologists to ask "if we integrate conversations amongst *people* using these temporal as well as spatial decoupling techniques, why don't we do the same with process-to-process conversations?".
There is no reason why we can't. We just need to STOP thinking of the Web/Internet as a synchronous modality. All the bits are in place. We know how to do reliable messaging. Its at least a thirty year old technology. We know how to represent dataflows - its called XML. Whats left? Just the rotation, through about 180 degrees, of the heads of a lot of young software developers.
N nodes. Everyone can talk to everyone else. Value = square(N). (Metcalf)
N nodes. Everyone can form groups with two or more members for fun and/or profit. Value = pow(2,n). (Reed)
The latter grows significantly faster than the former as N increases.
To form groups you need a virtual *place* decoupled from the processes involved. In synchronous (value N squared) integration, there is no such place - its in the state space of the processes themselves. In 2 to the N integration there is such a place - it is in the temporally decoupled message store formed by the groups.
Reliable messaging will be the next big thing on the Web. URIs will increasingly be seen as entry points (via two phase commit protocols) to unbounded message queues fed on by processes.
The response part of HTTPs request/response protocol will increasingly mean "Got the message, heres your tracking number. Will get back to you." rather than "Got the message, here is the response to your request.".
"The radical change was de-coupling groups in space and time. To get a conversation going around a conference table or campfire, you need to gather everyone in the same place at the same moment. By undoing those restrictions, the internet has ushered in a host of new social patterns, from the mailing list to the chat room to the weblog"
It also arguably has caused technologists to ask "if we integrate conversations amongst *people* using these temporal as well as spatial decoupling techniques, why don't we do the same with process-to-process conversations?".
There is no reason why we can't. We just need to STOP thinking of the Web/Internet as a synchronous modality. All the bits are in place. We know how to do reliable messaging. Its at least a thirty year old technology. We know how to represent dataflows - its called XML. Whats left? Just the rotation, through about 180 degrees, of the heads of a lot of young software developers.
N nodes. Everyone can talk to everyone else. Value = square(N). (Metcalf)
N nodes. Everyone can form groups with two or more members for fun and/or profit. Value = pow(2,n). (Reed)
The latter grows significantly faster than the former as N increases.
To form groups you need a virtual *place* decoupled from the processes involved. In synchronous (value N squared) integration, there is no such place - its in the state space of the processes themselves. In 2 to the N integration there is such a place - it is in the temporally decoupled message store formed by the groups.
Reliable messaging will be the next big thing on the Web. URIs will increasingly be seen as entry points (via two phase commit protocols) to unbounded message queues fed on by processes.
The response part of HTTPs request/response protocol will increasingly mean "Got the message, heres your tracking number. Will get back to you." rather than "Got the message, here is the response to your request.".
Sunday, April 20, 2003
Pronouncing 'Propylon'
Subscribe to:
Posts (Atom)