Previous / Next


Scripting News, the weblog started in 1997 that bootstrapped the blogging revolution.
Continuing with codecasting

Two changes to how the feed is generated. 1. Only output a part once, no need to update a part more than once, when updating, the last version will overwrite all previous versions. 2. Because of the first change, we have to change the order of the feed to reverse-chronologic. The result of this changes is that the size of the feed decreases, and the time spent processing it on updating decreases, and the cost of running the server decreases. A three-way win, so an obvious improvement.  Permanent link to this item in the archive.
If all goes well, I'll release the client code to OPML Editor users. It won't be turned on by default, but I will turn it on in all my copies of the OPML Editor, so it can get a good test before deploying to user sites. Permanent link to this item in the archive.
People ask what's so great about codecasting, and the answer is, for users, nothing in particular. For developers who manage environments with users who need to update frequently, it might cut the cost of providing updates. For me, it certainly will cut my costs, and since the software that I will update is open source, and produces no revenue, cutting costs means I have more money to go to the movies, eat out, buy toys, pay for health insurance, save for retirement, give to good causes. I write about stuff on my blog because I like to keep a record of my work, so it may not make sense to you, or even seem like a good idea, if so, so be it.  Permanent link to this item in the archive.
Actually, there is an advantage for users. The current method of updating requires the user's app to call teh server on port 5337, but we've received complaints that some corporate firewalls don't allow traffic on that port (contradicting the assumption, btw, that some critics of XML-RPC offer, saying we're just tunneling over port 80). Using RSS and a plain old web server, now we really are doing updates on port 80 and the corporate firewalls won't have any issues with it. ";->" Permanent link to this item in the archive.
Another reason I document my work here is so that I can include pointers in my comments, saving me having to document my work twice.  Permanent link to this item in the archive.



     

Last update: Thursday, June 3, 2010; 4:00:30 PM



~About the Author~

A picture named dave.jpgDave Winer, 55, is a visiting scholar at NYU's Arthur L. Carter Journalism Institute. He pioneered the development of weblogs, syndication (RSS), podcasting, outlining, and web content management software; former contributing editor at Wired Magazine, research fellow at Harvard Law School, entrepreneur, and investor in web media companies. A native New Yorker, he received a Master's in Computer Science from the University of Wisconsin, a Bachelor's in Mathematics from Tulane University and currently lives in New York City.

"The protoblogger." - NY Times.

"The father of modern-day content distribution." - PC World.

One of BusinessWeek's 25 Most Influential People on the Web.

"Helped popularize blogging, podcasting and RSS." - Time.

"The father of blogging and RSS." - BBC.

"RSS was born in 1997 out of the confluence of Dave Winer's 'Really Simple Syndication' technology, used to push out blog updates, and Netscape's 'Rich Site Summary', which allowed users to create custom Netscape home pages with regularly updated data flows." - Tim O'Reilly.

Mail: Mailto icon scriptingnews1mail at gmail dot com.

February 2007
Sun
Mon
Tue
Wed
Thu
Fri
Sat
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
 
Jan   Mar


RSS feed for Scripting News



© Copyright 1997-2010 Dave Winer. Last build: 6/3/10; 10:17:11 PM. "It's even worse than it appears."


Previous / Next