<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Chinese Travel Website Lost CNY60 Million Over Two Years</title>
	<atom:link href="http://www.chinatechnews.com/2007/03/20/5130-chinese-travel-website-lost-rmb60-million-over-two-years/feed" rel="self" type="application/rss+xml" />
	<link>http://www.chinatechnews.com/2007/03/20/5130-chinese-travel-website-lost-rmb60-million-over-two-years</link>
	<description>The Technology Source for the Latest Chinese News on Internet, Computers, Digital, Science, Electronics, Law, Security, Software, Web 2.0, Telecom, and Wireless Industries</description>
	<lastBuildDate>Sun, 05 Feb 2012 18:03:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Niner</title>
		<link>http://www.chinatechnews.com/2007/03/20/5130-chinese-travel-website-lost-rmb60-million-over-two-years#comment-3303</link>
		<dc:creator>Niner</dc:creator>
		<pubDate>Tue, 20 Mar 2007 22:20:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.chinatechnews.com/2007/03/20/5130-chinese-travel-website-lost-rmb60-million-over-two-years/#comment-3303</guid>
		<description>Any info on elong, ctrip or yoee? elong appears to be struggling against ctrip because it has not as good reputation but I never hear anything about yoee which is rumored to be bigger than these two chinese travel websites. Do you have more info about this company?</description>
		<content:encoded><![CDATA[<p>Any info on elong, ctrip or yoee? elong appears to be struggling against ctrip because it has not as good reputation but I never hear anything about yoee which is rumored to be bigger than these two chinese travel websites. Do you have more info about this company?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

