<?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: The search for the IMS/NGN application: A multimedia version of Kindle (Amazon book reader)</title>
	<atom:link href="http://www.opengardensblog.futuretext.com/archives/2008/10/the_search_for.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.opengardensblog.futuretext.com/archives/2008/10/the_search_for.html</link>
	<description>Wireless mobility - Innovation - Digital convergence - mobile web 2.0</description>
	<lastBuildDate>Thu, 19 Jan 2012 13:47:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Saul Labajo</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/10/the_search_for.html/comment-page-1#comment-1658</link>
		<dc:creator>Saul Labajo</dc:creator>
		<pubDate>Thu, 30 Oct 2008 12:22:26 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/10/the_search_for.html#comment-1658</guid>
		<description>I totally agree with this post, mainly with the first assertion, I think it clearly aims to the way applications should be built: with a network agnostic philosophy in mind.
I found the characteristics you suggest an IMS application should have most interesting because at Solaiemes we have developed mobile technology infraestructure with exactly those characteristics in mind.
Two of our product lines: LiveServe and the recently announced VoxServe are exactly what you say: session based, and allows serverperson  kind of services. The first one leverages Videoshare to implement services like real time videoblogging, and the second one leverages PTT technology to integrate it with IVR, CTI or just implement real time audioblogging.
And I am specially glad to see that in your last point you aim to a &quot;multimedia networked book reader&quot;, because that is one of the services that can be implemented using our third product: AVISG. This is a mobile content push platform that allows pushing multimedia content to a mobile web browser. We are using it to implement rich media alerts and multimodal services, but it can easly be used to implement some multimedia mobile book reader (given that target devices have a good enough screen and browser).
</description>
		<content:encoded><![CDATA[<p>I totally agree with this post, mainly with the first assertion, I think it clearly aims to the way applications should be built: with a network agnostic philosophy in mind.<br />
I found the characteristics you suggest an IMS application should have most interesting because at Solaiemes we have developed mobile technology infraestructure with exactly those characteristics in mind.<br />
Two of our product lines: LiveServe and the recently announced VoxServe are exactly what you say: session based, and allows serverperson  kind of services. The first one leverages Videoshare to implement services like real time videoblogging, and the second one leverages PTT technology to integrate it with IVR, CTI or just implement real time audioblogging.<br />
And I am specially glad to see that in your last point you aim to a &#8220;multimedia networked book reader&#8221;, because that is one of the services that can be implemented using our third product: AVISG. This is a mobile content push platform that allows pushing multimedia content to a mobile web browser. We are using it to implement rich media alerts and multimodal services, but it can easly be used to implement some multimedia mobile book reader (given that target devices have a good enough screen and browser).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
