Comments on: Building obex-method http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/ Random stuff Wed, 28 Oct 2009 02:53:32 +0800 http://wordpress.org/?v=2.8.5.2 hourly 1 By: pel http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/comment-page-1/#comment-252 pel Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/#comment-252 Wow.<br/>This is seriously wonderfull!<p/>Now I'll have to install edgy on a machine this weekend :) Wow.
This is seriously wonderfull!

Now I’ll have to install edgy on a machine this weekend :)

]]> By: Johan Hedberg http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/comment-page-1/#comment-253 Johan Hedberg Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/#comment-253 I took a look at the code and it looks good. One thing however:<p/>About the "NFTP" service identifier, that's actually something that btcond supported but hcid doesn't. You'll have to give the exact UUID-128 to hcid instead as<br/>"00005005-0000-1000-8000-0002ee000001" (I hope that's correct).<p/>What it's about: some Nokia Symbian phones have two OBEX FTP services: one identified with the normal UUID and another with a Nokia specific 128 bit UUID. The service found behind the normal identifier is very limited in features on these phones while the other one supports full OBEX FTP (don't ask me why).<br/> I took a look at the code and it looks good. One thing however:

About the “NFTP” service identifier, that’s actually something that btcond supported but hcid doesn’t. You’ll have to give the exact UUID-128 to hcid instead as
“00005005-0000-1000-8000-0002ee000001″ (I hope that’s correct).

What it’s about: some Nokia Symbian phones have two OBEX FTP services: one identified with the normal UUID and another with a Nokia specific 128 bit UUID. The service found behind the normal identifier is very limited in features on these phones while the other one supports full OBEX FTP (don’t ask me why).

]]> By: Wout http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/comment-page-1/#comment-254 Wout Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/#comment-254 Thank you man. You're awsome.... I've installed the software succesfully and everything works. Great.....<p/>B.t.w. mine gives me the full name after a while... and it's fully useable in nautilus. (Pretty stable...)<br/>I'f you wan't some testers just let me know....(just say so on your blog.... )<br/>GReat great great.... Thank you man. You’re awsome…. I’ve installed the software succesfully and everything works. Great…..

B.t.w. mine gives me the full name after a while… and it’s fully useable in nautilus. (Pretty stable…)
I’f you wan’t some testers just let me know….(just say so on your blog…. )
GReat great great….

]]> By: Andrew Jorgensen http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/comment-page-1/#comment-255 Andrew Jorgensen Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/#comment-255 Thanks! This is awesome. I've been thinking for some time now, though, that OBEX != bluetooth.<p/>There are at least four other media commonly (or less commonly) used for OBEX: USB, IrDA, Serial, and TCP/IP. All of these are supported by OpenOBEX.<p/>I've been told that IrDA is somewhat harder to deal with but USB should be pretty easy. Serial might not be worth implementing. TCP/IP, if supported at all, probably doesn't need to be discoverable (unless of course it's advertised through mDNS). Thanks! This is awesome. I’ve been thinking for some time now, though, that OBEX != bluetooth.

There are at least four other media commonly (or less commonly) used for OBEX: USB, IrDA, Serial, and TCP/IP. All of these are supported by OpenOBEX.

I’ve been told that IrDA is somewhat harder to deal with but USB should be pretty easy. Serial might not be worth implementing. TCP/IP, if supported at all, probably doesn’t need to be discoverable (unless of course it’s advertised through mDNS).

]]> By: Alex Kanavin http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/comment-page-1/#comment-256 Alex Kanavin Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/#comment-256 USB should use a different approach: mount it as a filesystem through FUSE/obexfs. I'll check out how it all works USB should use a different approach: mount it as a filesystem through FUSE/obexfs. I’ll check out how it all works

]]> By: James Henstridge http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/comment-page-1/#comment-257 James Henstridge Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/#comment-257 Wout: yeah. I implemented that a bit after posting this article.<p/>Andrew/Alex: Matthew Garrett has plans to add bluetooth device support to HAL, which would help here. If I can look up IrDA OBEX and Bluetooth OBEX devices in the HAL hardware database by some property, then it should be possible to support both: the only bluetooth specific code is for listing the paired devices and creating RFCOMM connections. Wout: yeah. I implemented that a bit after posting this article.

Andrew/Alex: Matthew Garrett has plans to add bluetooth device support to HAL, which would help here. If I can look up IrDA OBEX and Bluetooth OBEX devices in the HAL hardware database by some property, then it should be possible to support both: the only bluetooth specific code is for listing the paired devices and creating RFCOMM connections.

]]> By: clp http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/comment-page-1/#comment-258 clp Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/#comment-258 I get this message in nautilus...<p/>obex:///" is not a valid location.<p/><br/>what's wrong?<p/>How do I enable the gnome-vfs-2.0 modules?<p/>Salu2 clp ;) I get this message in nautilus…

obex:///” is not a valid location.

what’s wrong?

How do I enable the gnome-vfs-2.0 modules?

Salu2 clp ;)

]]> By: Andrew Jorgensen http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/comment-page-1/#comment-259 Andrew Jorgensen Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/#comment-259 clp: I had the same problem at first. Trouble was that by default things get installed in /usr/local. Try the following:<p/>./configure --sysconfdir=/etc --prefix=/usr clp: I had the same problem at first. Trouble was that by default things get installed in /usr/local. Try the following:

./configure –sysconfdir=/etc –prefix=/usr

]]> By: clp http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/comment-page-1/#comment-260 clp Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/#comment-260 A lot of thanks, Andrew!<p/>> ./configure --sysconfdir=/etc --prefix=/usr<p/>It's a great job!<p/> A lot of thanks, Andrew!

> ./configure –sysconfdir=/etc –prefix=/usr

It’s a great job!

]]> By: clp http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/comment-page-1/#comment-261 clp Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/10/20/building-obex-method/#comment-261 In amd64 architecture I get this problem in oss-gwobex compilation:<p/>autoreconf2.50: running: /usr/bin/autoconf<br/>configure.ac:11: error: possibly undefined macro: AC_PROG_LIBTOOL<br/> If this token and others are legitimate, please use m4_pattern_allow.<br/> See the Autoconf documentation.<br/>autoreconf2.50: /usr/bin/autoconf failed with exit status: 1<p/>Salu2 clp ;) In amd64 architecture I get this problem in oss-gwobex compilation:

autoreconf2.50: running: /usr/bin/autoconf
configure.ac:11: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf2.50: /usr/bin/autoconf failed with exit status: 1

Salu2 clp ;)

]]>