<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: obex-data-server 0.2</title>
	<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/</link>
	<description></description>
	<pubDate>Thu, 20 Nov 2008 21:41:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Robert</title>
		<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-111</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 21 Feb 2008 18:51:23 +0000</pubDate>
		<guid>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-111</guid>
		<description>*two thumbs up.</description>
		<content:encoded><![CDATA[<p>*two thumbs up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-110</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 21 Feb 2008 18:45:46 +0000</pubDate>
		<guid>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-110</guid>
		<description>Yes, this is possible with ods.</description>
		<content:encoded><![CDATA[<p>Yes, this is possible with ods.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-109</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 21 Feb 2008 18:41:29 +0000</pubDate>
		<guid>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-109</guid>
		<description>Hello Tadas,

I hope you are well and having a productive week. I wanted to ask you a question about the ODS. I'm sorry I've not be able to investigate this first hand but I'm still waiting on the Debian package to be completed so havnt been able to just yet. I'm trying to understand what OSD can achieve to see if it fits my requiments.

Am I correct to assume that due to this being a DBUS service that it is totaly asynchoronous? in as much that I would be able to push a file (in theory) to multiple devices almost symultaniously?

For instance, I regularly find myself sending a file to both myself and my colleague in the office here, it would be great if I could build so small app so that it transmits the file to both phones at the same time.

Does ODS offer this kind of functionality?

Thanks Tadas,

Robert</description>
		<content:encoded><![CDATA[<p>Hello Tadas,</p>
<p>I hope you are well and having a productive week. I wanted to ask you a question about the ODS. I&#8217;m sorry I&#8217;ve not be able to investigate this first hand but I&#8217;m still waiting on the Debian package to be completed so havnt been able to just yet. I&#8217;m trying to understand what OSD can achieve to see if it fits my requiments.</p>
<p>Am I correct to assume that due to this being a DBUS service that it is totaly asynchoronous? in as much that I would be able to push a file (in theory) to multiple devices almost symultaniously?</p>
<p>For instance, I regularly find myself sending a file to both myself and my colleague in the office here, it would be great if I could build so small app so that it transmits the file to both phones at the same time.</p>
<p>Does ODS offer this kind of functionality?</p>
<p>Thanks Tadas,</p>
<p>Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-71</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Fri, 15 Feb 2008 18:23:03 +0000</pubDate>
		<guid>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-71</guid>
		<description>Memory bugs are the spice of life :-D

What is this capability object support that you mentioned? what does it do?

Cheers for all your work on this Tadas, if there is anything any of us can do to help you out then let us know.

Rob</description>
		<content:encoded><![CDATA[<p>Memory bugs are the spice of life <img src='http://tadas.dailyda.com/blog/wp-includes/images/smilies/icon_biggrin.gif' alt=':-D' class='wp-smiley' /> </p>
<p>What is this capability object support that you mentioned? what does it do?</p>
<p>Cheers for all your work on this Tadas, if there is anything any of us can do to help you out then let us know.</p>
<p>Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-70</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 15 Feb 2008 18:12:09 +0000</pubDate>
		<guid>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-70</guid>
		<description>It might be coming along nicely, but I have some nasty memory bugs still there.. They come as a prize for using dbus-glib bindings :D Anyway, I recon this feature will make it to 0.3 release (which will hopefully also feature capability object support in server).

Cheers,
Tadas</description>
		<content:encoded><![CDATA[<p>It might be coming along nicely, but I have some nasty memory bugs still there.. They come as a prize for using dbus-glib bindings <img src='http://tadas.dailyda.com/blog/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> Anyway, I recon this feature will make it to 0.3 release (which will hopefully also feature capability object support in server).</p>
<p>Cheers,<br />
Tadas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manuel Naranjo</title>
		<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-69</link>
		<dc:creator>Manuel Naranjo</dc:creator>
		<pubDate>Fri, 15 Feb 2008 18:07:46 +0000</pubDate>
		<guid>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-69</guid>
		<description>I agree, I was thinking to add this stuff to CreateBluetoothSession and not to another place.</description>
		<content:encoded><![CDATA[<p>I agree, I was thinking to add this stuff to CreateBluetoothSession and not to another place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-68</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Fri, 15 Feb 2008 18:07:30 +0000</pubDate>
		<guid>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-68</guid>
		<description>Yeah I think you are right Tadas,

That would work just great I'm sure.

I really look forward to playing around with this API, it seems to be comming along really nicely.

Robert</description>
		<content:encoded><![CDATA[<p>Yeah I think you are right Tadas,</p>
<p>That would work just great I&#8217;m sure.</p>
<p>I really look forward to playing around with this API, it seems to be comming along really nicely.</p>
<p>Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-67</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 15 Feb 2008 16:37:16 +0000</pubDate>
		<guid>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-67</guid>
		<description>ods has to be as much transport independent as possible. That is, transport specific stuff should only be used in Manager object. I just noticed, that I did a bad thing in 0.2 release, where Server.Start method has bluetooth specific option (require_pairing). That's bad. Thinks like ‘/org/openobex/hci1′ are bad too. The only way to go is to add one more argument to CreateBluetoothSession function.</description>
		<content:encoded><![CDATA[<p>ods has to be as much transport independent as possible. That is, transport specific stuff should only be used in Manager object. I just noticed, that I did a bad thing in 0.2 release, where Server.Start method has bluetooth specific option (require_pairing). That&#8217;s bad. Thinks like ‘/org/openobex/hci1′ are bad too. The only way to go is to add one more argument to CreateBluetoothSession function.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manuel Naranjo</title>
		<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-66</link>
		<dc:creator>Manuel Naranjo</dc:creator>
		<pubDate>Fri, 15 Feb 2008 15:56:21 +0000</pubDate>
		<guid>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-66</guid>
		<description>Mhh right, that's something that might be needed to implement, I wonder how it should be done only.
We can't add a stuff to the bluez api as ods isn't part of BlueZ. Maybe the get_object thing makes sense, but instead of '/org/openobex' I would use '/org/bluez/hciX' then we are more friendly with BlueZ api.</description>
		<content:encoded><![CDATA[<p>Mhh right, that&#8217;s something that might be needed to implement, I wonder how it should be done only.<br />
We can&#8217;t add a stuff to the bluez api as ods isn&#8217;t part of BlueZ. Maybe the get_object thing makes sense, but instead of &#8216;/org/openobex&#8217; I would use &#8216;/org/bluez/hciX&#8217; then we are more friendly with BlueZ api.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-65</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 14 Feb 2008 16:51:28 +0000</pubDate>
		<guid>http://tadas.dailyda.com/blog/2008/02/12/obex-data-server-02/#comment-65</guid>
		<description>Thanks for the reply Tadas,

Being able to specify the adapter would be a great help. I guess that one way in which you could implement this would be to add a fromDevice() method which sets a device to be used. This would work nicely as it wouldnt break anyone using previous versions as it could default to the default bluez adapter.

Alternativly, perhaps it could be integrated in a similar way to the bluez adapter interfaces where we create an object such as get_object('org.openobex', '/org/openobex/hci1') or somthing along those lines?

Cheers Tadas,

Robert</description>
		<content:encoded><![CDATA[<p>Thanks for the reply Tadas,</p>
<p>Being able to specify the adapter would be a great help. I guess that one way in which you could implement this would be to add a fromDevice() method which sets a device to be used. This would work nicely as it wouldnt break anyone using previous versions as it could default to the default bluez adapter.</p>
<p>Alternativly, perhaps it could be integrated in a similar way to the bluez adapter interfaces where we create an object such as get_object(&#8217;org.openobex&#8217;, &#8216;/org/openobex/hci1&#8242;) or somthing along those lines?</p>
<p>Cheers Tadas,</p>
<p>Robert</p>
]]></content:encoded>
	</item>
</channel>
</rss>
