Source favicon23:35 「我對華視公共化的一些看法」 » ilyagram
「....無線電視台有兩塊優勢,一是高畫質電視,另一則是手機看電視的行動市場,商機很大,大到牽涉到電信業者、廣播業者、有線電視業者、手機製造商、工研院、內容業者等全包了進來,總產值絕對會超出新聞局現在投資的九十二億要多出幾千億的商機來,要懂得這一點者,同時得對數位科技、媒體和管理都懂,才能說得清楚,我忝為國家手機看電視(DVB-H)研究計畫的主持人,不得不說兩句話。  如果公共化是讓華視不能有商業經營模式,那麼前述的商機就沒了,這對國家未來影嚮甚鉅。  現有一種怪的想法,只想把頻道公共化,電視環境就好起來了,甚至要公視來接收華視,或者說,一個董事會來管公視與華視,這就令我憂心忡忡了。  營利和非營利是兩回事,營利要用公司來經營,非營利則得設財團法人基金會,這兩種制度是不同的,董事的組成也不同。許多非營利的負責人通常不是從我們這些有MBA背景的人,要求ROE,講究EPS的態度來經營的,假如所謂的公共化就等於公視化,我很懷疑,這豈不是叫公務員去做生意?  當然,公眾利益和追求最大利潤也不是不能並存,但不能把兩個為了不同目標的公司硬生生的併在一起,形成一個董事會,那董事的組成,就可有得吵了,最後會不會害了公共化的美意?實在很難說。....」 魚腸劍譜,魚夫。「我對華視公共化的一些看法」。
Source favicon23:05 我有怪癖吗? » 桑林志
年少一点的时候,可以列举出不少怪癖,也常会被人认作怪人,多少还以此为荣。但是现在,让我列举出5个怪癖,还不容易。原因大约有二:工作,成家,为人父后,已经被磨光了;或者怪癖还在,但是自己已经见怪不怪了。 1、爱睡觉。三十多人了,每天不睡够9小时,一天都不高兴; 2、不爱问。新浪爱问,但是我不爱问。典型的是不问路。非到不得已,我是不会张嘴的。看见Ma Yue也这毛病; 3、反应慢。常常表现得荣辱不惊,沉着冷静,但其实是反应慢而已; 4、 5、 就想起三条了,等再有再添上。 其实我不大喜欢这股风,这让我想起一种垃圾邮件:“……收到这封邮件,请转发给其它5个人……” 我就不按规则再点5个了。如果这样的活动是社会性的一种体现的话,那我可能是反党反社会的。:)
Source favicon22:27 我喜欢看木木的Blog » Andy's blog

木木(木木:一个视频舞女的身体日记)说:

如果你觉得我的乳房好看,那么我顺便也让你看看我的文章,如果你喜欢我的文章,我会感动地把乳房也送给你看(乳房与文章

我说:

正经的时候,觉得木木是个有思想、有才华、有觉悟(我是舞女我是党员)、甚至有点儿小资的女人(当白毛女也能穿上GUCCI )。同样也生活在上海,从她的Blog里也能发现上海很多有趣的人、事或者地方,比如《你革你的命我色我的情》提到的福州路和我们的革命先辈们,所以我喜欢看木木的Blog。

不正经的时候,觉得木木的身材是不错,尤其是(oYo),至少拼得过那几位大姐(都是出来混的),那些照片也并不是很色情,点到为止,也很真实,所以我喜欢看木木的Blog。

看过很多日本AV女优的Blog(比如南波杏的Blog),网下,她们拍了很多18禁的AV和写真,但在网上,个人Blog中反而表现得很清纯,很少有暴露的图片,写的内容也是生活中一些琐事,比如看什么书、吃什么、去哪玩之类的。也许在网下,每个人都有许多不能做的事情、不能说的话吧,所以只好在虚拟的网络上完成心愿。那木木呢?和她们相反吗?网下,我们能找到那些AV女优的AV和写真集,那木木呢?将来能不能找到她的“清纯的”杂文集:)

我是国产永久牌自行车(光棍),所以没什么可担心的^_^(暑期末的爱情

Source favicon21:53 用Java进行基于浏览器的桌面应用程序开发(Browser-based desktop application development with java) » Andy's blog

作者:Andy(http://blog.xintiantang.com/andy),版权所有,转载请先联系我

这篇文章于2005/08/30 20:00开始,计划在一个月内完成,所以将会人工置顶。内容有点儿乱,先把想的和做的记下来,然后再慢慢整理。同时欢迎提出你的看法。更新记录:2005/08/30 20:00,2005/08/31 14:45,2005/08/31 21:21,2005/09/01 16:24,2005/09/01 21:53

对于普通用户来说,使用传统的桌面应用程序(可能采用不同语言和工具开发的)可能存在这样那样的限制,比如界面风格千变万化、操作习惯不统一、学习难度大、无法或很难和外部应用通信等。而传统的服务器端应用程序或网站也存在许多限制,比如网络连通可能出现问题、响应速度慢、不能保证服务器端始终可用、担心数据安全和个人隐私问题、不够灵活、使用不方便等。

 而基于浏览器的桌面应用程序正是综合桌面应用程序和服务器端应用程序的功能产生的。它包含以下优点:

基于浏览器的桌面应用程序(Browser-based desktop application)的定义:一个包含嵌入式网站服务器(Embedded web server)的能够在浏览器内的客户端的独立运行(Stand alone)的应用程序。

我把基于浏览器的桌面应用程序(Browser-based desktop application)简称为BBDA。其实BBDA和AJAX技术一样,也是一个buzzword,而不是什么新技术,只不过把几种通用的软件或技术组合在一起而已。和传统的重量级的Portal系统不同的是,BBDA是轻量级网络应用(Light weight web application),XML(Feed / RSS / XML-RPC / SOAP)是联系各个服务或应用的纽带。

其实,BBDA很符合目前热炒的WebOS(基于网络浏览器的操作系统)的特性,这方面Google做了个最好的Demo:Google Desktop, 在GD中,一切内容的表现都是网页(虽然隐藏了浏览器),并且很容易和Google网站进行通信(比如同时搜索本地和搜索Web,利用Feed(RSS)或XML-PRC或SOAP之类的协议读新闻、邮件、天气预报、股票行情等,微软该称RSS为Feed好像很有道理吧?)。现在GDS(Google Desktop Search)只是GD的一个模块而已,百度的桌面搜索只是单纯地模仿了GDS,却没有猜到原来Google是要做GD,好傻的百度。Google这几年的收购和挖人活动(Google宽带, Google browser等),看来一切都是为了WebOS而努力。这里顺便说一下Yahoo刚收购的Konfabulator,Konfabulator和GD有很大不同,我觉得它只是包含许多小软件或和网站交互的工具,只是个玩具箱而已,要做WebOS靠这个可以吗?看来Yahoo的眼光似乎始终不如Google。找到这篇文章:GoogleOS? YahooOS? MozillaOS? WebOS? 居然和我的想法如此相似(写这个之前我绝对没看过这篇文章)!

由于我主要做Java开发,所以只列出可能涉及的Java软件包:Browser(IE/FireFox), JDK, Tomcat/Jetty, HSQLDB/Apache Derby, Hibernate, Spring, Groovy, DOM4J,Apache Http Client, Lucene, Struts/WebWork/JSF/Tapestry/Wicket/Flex&Laszlo(Flash RIA), DWR(AJAX), Apache Web Services(SOAP/XML-RPC), Apache POI(Word/Excel/ PDF), MP3 ID TAG 3 lib ,JPEG EXIF lib...

我的目的是组合几种通用的JAVA软件,用来进行快速的BBDA开发。对于开发者而言,只要选好合适的软件,并合理组合起来,完全可以达到或超过Ruby on rails的功能和开发效率。同时,对于普通用户而言,只要打开浏览器输入http://localhost就会进入Dashboard(ProtoPage是个很好的Prototype^_^),然后就可以管理日记(blog)、日历、通讯录、照片(flickr?)、音乐(itunes?)、文件、网摘(delicious?)、阅读订阅的RSS(bloglines?)、查看邮件(web mail)、新闻之类等,并可以进行搜索、共享、发布、与外部应用或网站同步等,构成一个完整的个人门户系统(Personal portal),XML(Feed / RSS / XML-RPC / SOAP)是联系各个服务或应用的纽带。。

画了个草图(持续修改中):

BBDA

接下来我会发布一个开发BBDA的基础软件包(将会包含一个简单的相册的BBDA),下面是我对基础软件包的说明。

关于嵌入式网站服务器(Embedded web server):

我这几天试用了Jetty和Tomcat。总以为Jetty很小呢,最适合做BBDA呢,结果发现软件包也很大了,另外很多功能不如Tomcat,Tomcat Embed 5.5由于使用Ecipse JDT,现在已经很小了(3M左右),而且标准,所以选了Tomcat Embed(这里下载)。下面的代码是Tomcat Embed的启动程序。

Start.java:

package com.terac.tomcat;
import java.net.InetAddress;
import java.net.UnknownHostException;
import org.apache.catalina.Context;
import org.apache.catalina.Engine;
import org.apache.catalina.Host;
import org.apache.catalina.LifecycleException;
import org.apache.catalina.connector.Connector;
import org.apache.catalina.startup.Embedded;

public class Start {
 public static void main(String[] args) {
  try {
   String path = System.getProperty("SERVER_HOME");
   if(path!=null&&!"".equals(path)){    
    int port = Integer.parseInt(System.getProperty("SERVER_PORT","8080"));
    startTomcat(path,port);
   }   
  } catch (Exception e) {
   e.printStackTrace();
  }
 }
 private static void startTomcat(String path,int port) throws UnknownHostException,
   LifecycleException {
  System.setProperty("catalina.home", path);
  Embedded embedded = new Embedded();
  Engine engine = embedded.createEngine();
  engine.setName("Engine");
  Host host = embedded.createHost("localhost", "web");
  Context rootContext = embedded.createContext("", "");
  rootContext.setPrivileged(true);
  host.addChild(rootContext);
  engine.addChild(host);
  engine.setDefaultHost("localhost");
  embedded.addEngine(engine);
  Connector connector = embedded.createConnector((InetAddress) null,port, false);
  embedded.addConnector(connector);
  embedded.start();
 }
}

start.bat:

@set classpath=./lib/所有的jar文件
@java -DSERVER_HOME=%cd% -DSERVER_PORT=80 -classpath %classpath% com.terac.tomcat.Start

关于嵌入式数据库(Embeded database):

Apache Derby虽然比HSQLDB强大,但还是太大了,尤其是当用到IBM的JDBC Driver时。所以只好选HSQLDB。下面的代码是在Web应用程序启动时启动HSQLDB服务器。

HSQLDBServletContextListener.java:

还未整理好

web.xml中需要加入listener:

com.terac.hsqldb.HSQLDBServletContextListener

关于全文检索引擎(Full text search engine):

Apache Lucene应用广泛,也足够强大,高亮显示(Highlighting)需要自己实现,自动摘要(autosummarize)需要Classifier4j 。下面是常用类的封装代码:

Indexer.java:

还未整理好

Searcher.java:

还未整理好

Highlighter.java:

还未整理好

关于Shell:

有些时候,用户不满足已经有的服务,需要更灵活的、或者定制的功能,一个简单的、易学的、解释性的、交互式的Shell就显得很必要,比如Windows提供的cmd或Linux里的bash。研究了一下,发现Groovy正好能满足需要,“for (ch in "Hello world!") {println ch}”,这个稍微复杂点儿的Hello world很好懂吧?

关于计划任务(Schedule Task):

Windows里有计划任务,Linux里有Cron job,这个对于WebOS也是必须的,比如定时检查邮件,定时抓新闻等等,Spring framework封装了好几种Time service,足够了。

关于对象关系映射工具(OR mapping tools):

Hibernate是最常用最强大的工具。下面是Hibernate Session的封装代码:

HibernateUtil.java:

import net.sf.hibernate.HibernateException;
import net.sf.hibernate.SessionFactory;
import net.sf.hibernate.Session;
import net.sf.hibernate.cfg.Configuration;
import org.apache.log4j.Logger;

public class HibernateUtil {
 private static Log log = LogFactory.getLog(HibernateUtil.class); 
 public static final ThreadLocal threadSession = new ThreadLocal();
 private static final SessionFactory sessionFactory;
 static {
  try {
   sessionFactory = new Configuration().configure().buildSessionFactory();
  } catch (Throwable ex) {
   // We have to catch Throwable, otherwise we will miss
   // NoClassDefFoundError and other subclasses of Error
   log.error("Building SessionFactory failed.", ex);
   throw new ExceptionInInitializerError(ex);
  }
 }
    public static Session currentSession() throws HibernateException {       
        Session s = (Session) threadSession.get();
        if (s == null) {
            s = sessionFactory.openSession();
            threadSession.set(s);
        }
        return s;
    }
    public static void closeSession() throws HibernateException {
        Session s = (Session) session.get();
        session.set(null);
        if (s != null)
            s.close();
    }
}

关于模型-视图-控制框架(MVC framework):

现在的MVC framework太多了,传统的有Struts/WebWork,新的有JSF/Tapestry/Wicket/Flex&Laszlo(Flash RIA) ,Wicket网站列出了55种之多!我试过JSF,始终不能另我满意,正在尝试这个Wicket。

待续。。。

Source favicon18:42 Beijing Media Top Stories: Baghdad bridge stampede, new buses and pocelain pit ... » Danwei RSS 1.0
BMP050901S.jpg
Beijing Morning Post's cover, features a picture of bridage stampede in Baghdad.

1. More than 965 people were killed and hundreds more injured Wednesday morning when rumors of a suicide bomber provoked a frenzied stampede in a procession of Shiite pilgrims as they crossed a bridge in northern Baghdad;

2. Four color palates were decided for new Beijing bus, and the monthly tickets to be accepted by 350 buses equipped with air-conditioners;

3. About 1 million scraps of broken porcelain, some of which may be up to 800 years old, unearthed recently from an enormous pit in downtown Beijing;

4. A big ceremony was held to celebrate the 40th anniversary of the founding of the Tibet Autonomous Region, September 1;

5. The funeral of Chinese actor Fu Biao is held today in Babaoshan memorial park.

Source favicon15:57 Daily Links for 2005-08-31 » Jeremy Zawodny's blog
This is an automated daily posting... RSS from Yahoo! WeatherYay! (tags: rss, weather, yahoo) Old School vs. New School MarketingMike spotted a good chart (tags: blogging, marketing) Simpler Movable Type templatesa good way to understand what it takes to roll your own (tags: blogging, movabletype) MSN Search Introduces Feed Searchno fair! theirs isn't even vaporware! (tags: blogging, microsoft, msn, rss, search) USGS Real-Time Water Data for New Orleans, LAwatch the water rise... (tags: flood, hurricane, neworleans, usgs) Google Galvanizes Invention...
Source favicon14:52 RSS-Feed.org: Web based news aggregator » Tim Yang's Geek Blog

RSS-feed.org is a beta site that lets you create a publicly accessible webpage that shows news from all your favourite news sources — as long as they have an RSS feed. Right now RSS-feed.

Source favicon12:10 你想去Google工作吗? » Andy's blog

Larry Williams想去Google工作(详见Google jobs),他通过Google Jobs对Google的招聘职位统计了一下:

Programming languages

Skill Count
Python 98
C++ 98
Java 98
Perl 73
Javascript 45
PHP 26
C# 5
Ajax 1
Ruby 0

Operating systems

Skill Count
Linux 99
Windows 53
Mac 3
FreeBSD 1
Solaris 1

Other

Skill Count
XML 26
Struts 2

看来在Google里,Python,C++,Java还是王者,Linux用得最多,XML也很广泛,Struts居然也有(Google Ad Sense好像是用这个的吧?)。

看了Google在Mountain View总部的Java Engineer职位,发现我也可以啊:),我也喜欢 ten other great reasons,Google比国内公司要实际多了,如果Google是中国公司的话,估计招聘职位要求是这样的:

记得曾经问Leader我们公司总部也在MV,那周围都有什么大公司啊?他说周围只有一家大公司,那家公司就是Google。。。

Source favicon11:55 FeedBurner Redesign Unveiled » Burn This! - The FeedBurner Weblog

As we hinted yesterday, some changes have been afoot here at FeedBurner. It started with a new coffee maker that doesn't harm anyone pouring a cup of coffee before it's done brewing. This welcome enhancement was inevitably followed by thoughts of "Should we do for the site what we've done for the coffee?" We put our heads together, brought in some new and existing users to test our hunches, and a few weeks later we've got the redesigned FeedBurner application you can visit right now after you've logged in.

All of the changes have occurred below the “public surface” (what you see after signing in) — they are primarily changes to your feed configuration and account management experience. Our No. 1 goal was to make it easier to offer our publishers more new services and stats reporting tools in the coming months without further stretching the limits of socially appropriate vertical scrolling. So, instead of presenting all 15 of our services (and counting!) on one page, everything is now available from logically organized tabbed menus and sidebar. This is a more scalable solution and helps us keep up with our highly energetic Product Development and Engineering teams. See a service you want? Click its title, enter its options, and click its Activate button. It goes to work on your feed immediately. We have integrated the feed awareness and promotion capabilities into this management interface, and we have also tried to make solving feed problems easier with a new “Troubleshootize” feature for every feed you burn. We have simplified your account's My Feeds page to report circulation statistics at-a-glance and provide you with timely updates from FeedBurner headquarters.

The rest of the public website — outside of a signed-in user account — is unchanged. You can expect improvements there in the near term as we expand our services to reach new audiences and syndication markets. For now, all remains as it was.

One final note: there are no new publisher services effective with this launch — If you have a feed burned with us, it's completely unchanged. However, we hope future enhancements will be easier to apply.

For a quick guide to some of the key changes (and to help re-orient yourself), check out our redesign guide. Have comments for the design team? Send them in!

Source favicon11:42 StyleCatcher Updated » ProNet
We're glad to announce an update to the StyleCatcher plugin announced last week. StyleCatcher 1.01 fixes a number of little bugs, offers some helpful documentation in the README file about how to get started, and introduces a cool new feature:...
Source favicon11:02 用Blog作Marketing工具 » Jan's Tech Blog
近期正在隨Careertimes附送的雜誌INKY之上寫一些有關Blog如果應用在企業上的文章。寫了之後,就問了編輯大人,是否可以Post上Blog。幸得蒙允許,於是便在這兒分享。 第一編文章刊在INKY第31期,是這系列文章的一首篇。初談如何利用Blog作推廣產品或服務之用。同期,Jan亦寫了一篇《粵港同心打造「迪士尼新經濟」》。可惜,除了那大題目之外,Jan對自己寫的內文就不怎滿意,所以就不Post出來。為了方便大家閱讀,我除了將Scanning放在Flickr那邊之外,更直接將自己的原文Post在此Blog上。不過最重要的都是大家的意見。(注:原文是指筆者交稿給編輯時的版本,經編輯看過後,當然就更加流暢。)...
Source favicon09:54 Internet Connection Speeds at Work » Jeremy Zawodny's blog
Reason #618 to work at Yahoo: fast network connections. Just for kicks, I decided to use the BroadBandReports.com speed test to check the speed of the Internet connection as seen by my notebook. Roughly 80Mb/sec. Not bad. Not bad at all......
Source favicon09:13 个人门户,由输入到输出 » Xerdoc Together
总是喜欢拿技术上的东西来说,因为我觉得本质上,这些都是相通的。 对程序来说,归根结底就是数据(信息)的流动,两个最重要的环节就是数据的输入和输出。 对个人来说,也是一样的,他需要有输入和输出。对于输入来说,就是信息的获取。而输出呢,就是主动的自我意识的表达。我们每个人就像一个程序,根据自己获得的信息做出各种各样的输出 。 信息获取是Web1.0时代的主要需求,而到了Web2.0时代,用户意识的表达成了一个非常重要的需求,因此也就有了"An architecture of participation"。 就个人门户来说,也同样存在两个方面: 1)输入 这方面我用过Google ig,微软的Start 3,以及刚刚看到的Protopage。 "Garbage in, Garbage out",好的输入才能制造好的输出。对我来说,一个Protal就是一个强大到能够让我甘心把它设置为浏览器首页的东西,她应该包括邮件、Bookmarks、天气预报、股票、RSS支持、即事贴等等,当然,还有一个重要的因素就是速度不能过慢。 这样,带给我们的好处是: 节省了时间成本,可以在一页得到尽可能多的信息; 会有更好的用户体验。用户的网络活动由此发起,Portal将可以拿到很多用户的第一手资料,从而进行分析和有目的的信息的主动推送。 Google ig Google ig支持很多新闻源,支持RSS的导入(不过不支持OPML),支持Stock Market的定制。当然,最吸引我的还是GMail和Google Search History的集成。Gmail和Google Search都是杀手级的应用,因此Google ig推广起来,恐怕也更容易一些吧。遗憾的是,Google ig目前似乎问题还比较多,经常会出现“信息不可用”,比较扫兴。 Start 3 Start是微软的试验作品,非常酷,AJAX的应用非常恰当,看起来比Google ig要炫很多。Startlet做的都很有意思,特别是那个与MSN Virtual Earth结合的例子。Start的菜单中也包括MSN Search History,不过目前还不支持。当然,对于我这样一个习惯了使用Gmail和Google Search的人来说,如何将我从Gmail和Google Search吸引过来是个问题。 Protopage Protopage能够添加Bookmark,不过不支持RSS,最吸引我的是它的StickyNotes,就像我们平时的即事贴,终于,我可以把我的即事贴贴到了电脑屏幕上。对我来说,这是一个杀手级应用。 2)输出 在Web2.0时代,我们更需要别人的认可,需要自我意愿的表达,我们的个人门户就是这样一个舞台,一个展示自己的舞台(广告时间:心有多大,舞台就有多大 )。这个舞台上,你可以放自己的Blog,自己最近的照片,自己看过的文章,自己在听的音乐,自己在看的书,以及自己朋友们的文章,这是一个你自己的地盘,是别人了解你的窗口。 我理想中的这种个人Portal还是去中心化的,你个各种服务还是应该采用最流行,最棒的服务,同时采用Web Service或者RSS(RSS就像是一个Interface,使得你的各种服务的聚合成为可能。)将他们聚合到你自己的Portal上。比如,Bookmarks还是采用Del.icio.us,照片就放在Flickr上,读书交流用豆瓣,Podcasting用土豆,然后用RSS将他们聚合到你自己的Portal上,这就像你自己的一份报纸,你是主编,你负责将你的内容组织展现在你的朋友们眼前。当然,你也可以在你的报纸上放置自己的广告,只要不吓跑你的读者 。 Tags: Tech, Web2.0, Personal Portal, RSS, Blog, 个人门户 Tags: , , , , ,
Source favicon08:24 What to tell DMA Conference Attendees about Blogs? » Jeremy Zawodny's blog
It looks like I'm going to be on a panel called "Harnessing the Buzz Power of Blogs" at the 2005 Direct Marketing Association (DMA) Conference in Atlanta. The theme for this year appears to be "Learn to listen to your customer." My panel doesn't appear on the list yet, but I'm sure that'll be fixed before too long. Anyway, if you had the chance to talk to a room full of folks at such a conference, what would you...
Source favicon03:57 MSN Offering "Blog This" Button on News Stories » Jeremy Zawodny's blog
Wow, it's about time the big sites started doing this. Spotted over on the Microsoft Monitor weblog: Early this morning, I read up on the latest news about the aftermath of Hurricane Katrina. Of interest, interactive graphic over at MSNBC. Down in the lower right-hand corner is "Blog this," which if clicked logs the user into MSN Spaces (assuming he or she has a space) and fills in a post with title and link. User just needs to click save....
Source favicon02:54 Simple Example Templates for Movable Type 3.2 » ProNet
Chris Vannoy has posted some simple Movable Type templates based on the new default templates in Movable Type, but with much of the XHTML structure stripped out so they're easier to read. As Chris explains in his following post, they're...
Source favicon02:15 Raves for your Faves » Yahoo! Search blog
Here at Yahoo!, we've been working for many years on ways to enable people to exchange vital and useful information with each other, and the recent launch of Yahoo! Local, along with My Web and message boards on Yahoo! Travel...
Source favicon01:31 Powered by Google » Google Blog




This past weekend 10 Googlers competed at Hood to Coast - the largest relay race in the world - where more than 1,000 teams start at the top of Mt. Hood (11,249 feet) and race 200 miles to the coast of Oregon. This was our rookie year, and our team, "Powered by Google," included Nathan Stoll, Bismarck Lepe, David King, Katie Hotchkiss, Sean Knapp, Michaela Prescott, Natalie Criou, Dan Brown, Tyrona Heath, and me.



Armed with a flashlight and decked out in a reflective vest, Nathan started us off at 7:45 Friday night with a 6-mile run down the face of the mountain. The runners on deck hopped on Van #1 to cheer him on and meet him at the next exchange. The runners who weren't on call until the second stage headed to the nearest Best Western Pony Soldier Inn for some spaghetti and shut-eye.



At the sixth leg exchange Sean passed the baton to Michaela and the race continued through the midnight hour while our starters headed back to the Pony Soldier for a 60-minute power nap. After refueling on Red Bull, coffee, power gels, and turkey sandwiches from a nearby gas station mini-mart, we caught up with Van #2 as the sun rose over Portland. From there, through the dusty back roads and increasing temperatures, we continued passing the baton in 4-8 mile intervals.







It all went smoothly until we met an 18-minute logistical error at exchange 24 (read: we lost Van #2) and then had a flat tire at exchange 29. But we rebounded with solid performances in the final legs, making up much lost ground. Finally, cloaked in a Google jersey, our anchor leg, Sean, crossed the finish line in 22 hours, 19 minutes, and 17 seconds.



In the time it took us to reach the coast, we had each run an average of 20 miles at 6:48/mile. We captured a third place finish in the "corporate mixed" division, and a top 50 finish overall, out of 1,063 teams.







Not bad for a bunch of first-timers. Just wait until next year: we won't be rookies anymore.

^==Back Home: www.chedong.com

<== 2005-08-31

==> 2005-09-02