<?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: obex-data-server 0.3.2</title>
	<atom:link href="http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/feed/" rel="self" type="application/rss+xml" />
	<link>http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/</link>
	<description></description>
	<lastBuildDate>Mon, 05 Apr 2010 14:20:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: User links about "obex" on iLinkShare</title>
		<link>http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/comment-page-1/#comment-4783</link>
		<dc:creator>User links about "obex" on iLinkShare</dc:creator>
		<pubDate>Wed, 06 May 2009 01:01:24 +0000</pubDate>
		<guid isPermaLink="false">http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/#comment-4783</guid>
		<description>[...] votesHow to Beam Data Between Your Pocket PC and a Palm?&gt;&gt; saved by dcochranokwu 24 days ago3 votesobex-data-server 0.3.2&gt;&gt; saved by aranas 28 days ago4 votesBluetooth en Debian Lenny&gt;&gt; saved by ttrinoid 32 days ago1 [...]</description>
		<content:encoded><![CDATA[<p>[...] votesHow to Beam Data Between Your Pocket PC and a Palm?&gt;&gt; saved by dcochranokwu 24 days ago3 votesobex-data-server 0.3.2&gt;&gt; saved by aranas 28 days ago4 votesBluetooth en Debian Lenny&gt;&gt; saved by ttrinoid 32 days ago1 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manuel Naranjo</title>
		<link>http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/comment-page-1/#comment-778</link>
		<dc:creator>Manuel Naranjo</dc:creator>
		<pubDate>Fri, 27 Jun 2008 19:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/#comment-778</guid>
		<description>Everyone,

Guys I have to get out my hat and congratulate you all. 

Lots of bugs had been fixed, specially memory allocation stuff, I left a server running yesterday on the office, and after almost 24 hours, and after 400 sessions created it still works without any trouble.

I also checked with valgrind, and compared 0.3.1 and 0.3.2 and the difference is enormous, from lots of memory corruptions you have moved to 0. Incredible.

Great job everyone,

Thanks,
Manuel</description>
		<content:encoded><![CDATA[<p>Everyone,</p>
<p>Guys I have to get out my hat and congratulate you all. </p>
<p>Lots of bugs had been fixed, specially memory allocation stuff, I left a server running yesterday on the office, and after almost 24 hours, and after 400 sessions created it still works without any trouble.</p>
<p>I also checked with valgrind, and compared 0.3.1 and 0.3.2 and the difference is enormous, from lots of memory corruptions you have moved to 0. Incredible.</p>
<p>Great job everyone,</p>
<p>Thanks,<br />
Manuel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heston James</title>
		<link>http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/comment-page-1/#comment-776</link>
		<dc:creator>Heston James</dc:creator>
		<pubDate>Fri, 27 Jun 2008 07:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/#comment-776</guid>
		<description>Good Morning Tadas,

Congratulations on this release! I know you&#039;ve worked very hard to get it ready, we really appreciate the hard work, well done. *thumbs up

Heston</description>
		<content:encoded><![CDATA[<p>Good Morning Tadas,</p>
<p>Congratulations on this release! I know you&#8217;ve worked very hard to get it ready, we really appreciate the hard work, well done. *thumbs up</p>
<p>Heston</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/comment-page-1/#comment-765</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 25 Jun 2008 19:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/#comment-765</guid>
		<description>All crashers should be fixed in this release. Lots of work was needed and hopefully it works flawlessly now. Problem concerning not catching signals will be fixed in the next release as it requires API change.

Cheers,
Tadas</description>
		<content:encoded><![CDATA[<p>All crashers should be fixed in this release. Lots of work was needed and hopefully it works flawlessly now. Problem concerning not catching signals will be fixed in the next release as it requires API change.</p>
<p>Cheers,<br />
Tadas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manuel Naranjo</title>
		<link>http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/comment-page-1/#comment-763</link>
		<dc:creator>Manuel Naranjo</dc:creator>
		<pubDate>Wed, 25 Jun 2008 19:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://tadas.dailyda.com/blog/2008/06/25/obex-data-server-032/#comment-763</guid>
		<description>Hi Tadas,

So long with no talk, how are things?. 

As I told you before we were going to Chicago for a sensors expo. We had a fun time, during the 3 days the sensor lasted ODS received over 2k obex messages from 10 of our devices.

ODS was a bit unstable it crashed no less than 10 times during the expo. I&#039;m going to try this new version and tell you my results.

I tried debuggin and working on fixes to it, but it was impossible.

BTW to all those who all ready don&#039;t know. I&#039;ve found a work around to avoid loosing obex transfers. The solution is registering for dbus signals before the session object is created. I know this is not a nice looking solution, but it has 2 positives results. One is that you don&#039;t loose any message, the other one is that in cases when you&#039;re expecting to receive lots of transfers you are not registering/deregistering from dbus avoiding all the payload related to it.

If you want to take a look at the source it&#039;s available at: http://code.google.com/p/aircable/source/browse/tools/messages

Thanks and good luck to all of you,
Manuel Naranjo
www.aircable.net</description>
		<content:encoded><![CDATA[<p>Hi Tadas,</p>
<p>So long with no talk, how are things?. </p>
<p>As I told you before we were going to Chicago for a sensors expo. We had a fun time, during the 3 days the sensor lasted ODS received over 2k obex messages from 10 of our devices.</p>
<p>ODS was a bit unstable it crashed no less than 10 times during the expo. I&#8217;m going to try this new version and tell you my results.</p>
<p>I tried debuggin and working on fixes to it, but it was impossible.</p>
<p>BTW to all those who all ready don&#8217;t know. I&#8217;ve found a work around to avoid loosing obex transfers. The solution is registering for dbus signals before the session object is created. I know this is not a nice looking solution, but it has 2 positives results. One is that you don&#8217;t loose any message, the other one is that in cases when you&#8217;re expecting to receive lots of transfers you are not registering/deregistering from dbus avoiding all the payload related to it.</p>
<p>If you want to take a look at the source it&#8217;s available at: <a href="http://code.google.com/p/aircable/source/browse/tools/messages" rel="nofollow">http://code.google.com/p/aircable/source/browse/tools/messages</a></p>
<p>Thanks and good luck to all of you,<br />
Manuel Naranjo<br />
<a href="http://www.aircable.net" rel="nofollow">http://www.aircable.net</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
