openobex-users — The OpenOBEX users mailing list

[openobex-users] [KiiTos]お問い合わせ有難うございます

[KiiTos <in...@ki...>]

?? Karen liked you! Click Here: https://clck.ru/anhJS?pv5hv ??様

お問合せありがとうございます。
このメールは自動返信にてお送りしております。

改めて、担当よりご連絡させていただきますので今しばらくお待ちください。

―――――――――――――――――――――――――――――――――――――――――――――――――――
電話番号：104042805355
メールアドレス：ope...@li...

お問い合わせ内容
t7vid1
―――――――――――――――――――――――――――――――――――――――――――――――――――

※メールでの確認作業が遅れる場合もございます。
お急ぎの場合はお電話にてお問い合わせ下さい。
0495-23-3321

[openobex-users] 仲原病院│お問い合わせを受け付けました

[仲原病院 <nhp...@na...>]

この度は、仲原病院ホームページからのお問い合わせ、
まことにありがとうございます。

このメールは自動返信（控えメール）です。
内容を確認後、担当者よりご連絡を差し上げます。

お急ぎの方や、送信内容にご不明点がございましたら、
お電話でも受け付けております。

-------------------------------------------------------------------
お名前： ?? Irene liked you! Click Here: http://inx.lv/DJSF?ao7n3 ??
フリガナ：  tavrw44
E-mail： ope...@li...
電話番号： 248271221846
住所： 2qhx7yc9

件名： その他

メッセージ本文：
3q17pt3

-------------------------------------------------------------------

／以上です

==============================================
一般財団法人 福岡県社会保険医療協会
社会保険 仲原病院
〒811-2233　福岡県糟屋郡志免町別府北二丁目12番1号
TEL　092-621-2802（代表） / FAX　092-623-2247（代表）

ホームページ： http://nakabaru-hp.jp/
E-mail： nhp...@na...
==============================================

[openobex-users] [PATCH] Fixed udev rule by uaccess tag

[Cho, Yu-C. <ac...@su...>]

GROUP="plugdev" no longer exists, replace those by TAG+="uaccess"

Signed-off-by: Cho, Yu-Chen <ac...@su...>
---
 udev/openobex.rules.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/udev/openobex.rules.in b/udev/openobex.rules.in
index 9c83ed3..ffa9e1a 100644
--- a/udev/openobex.rules.in
+++ b/udev/openobex.rules.in
@@ -1,3 +1,3 @@
 #udev script to make USB CDC devices with OBEX accessible to users
 
-ACTION=="add", SUBSYSTEM=="usb", PROGRAM="@prefix@/sbin/obex-check-device $attr{idVendor} $attr{idProduct}", MODE="660", GROUP="plugdev"
+ACTION=="add", SUBSYSTEM=="usb", PROGRAM="@prefix@/sbin/obex-check-device $attr{idVendor} $attr{idProduct}", TAG+="uaccess"
-- 
1.8.4.5

Re: [openobex-users] File transfers on Android device do not work

[Hendrik S. <po...@he...>]

Am 03.08.2013 10:17, schrieb Malte Gell:
> Oh, it seems I was wrong. The file I tried to copy was a 3 or 7 MB mp3
> file, a fairly large thing.
>
> Now I tried to copy a 30 byte file and taaadaaaa, I could issue the ls
> -l command and the shell was not blocked.
>
> So it was the seize of the large file that made me think it did not
> work, actually the transfer is just slow like hell and has blocked the
> device.
>
> Bluetooth is great, but sooo slow....

Hi,

sorry for the long delay before answering.

Actually, it's not always bluetoth that is slow but often the involved 
programs use sub-optimal settings.

In case of Android, it usually uses a muuuuuch to low MTU (maximum 
transfer unit), e.g. when sending to it:
obex_parse_connectframe(): requested MTU=65534, used MTU=1024

:-/

HS

Re: [openobex-users] File transfers on Android device do not work

[Malte G. <mal...@gm...>]

Oh, it seems I was wrong. The file I tried to copy was a 3 or 7 MB mp3
file, a fairly large thing.

Now I tried to copy a 30 byte file and taaadaaaa, I could issue the ls
-l command and the shell was not blocked.

So it was the seize of the large file that made me think it did not
work, actually the transfer is just slow like hell and has blocked the
device.

Bluetooth is great, but sooo slow....

Malte

Re: [openobex-users] File transfers on Android device do not work

[Malte G. <mal...@gm...>]

Oh, just to clarify, I use Obex over bluetooth.

[openobex-users] File transfers on Android device do not work

[Malte G. <mal...@gm...>]

Hello!

I have a HTC One S with Android 4.1.1 and I mount it this way:

obexfs -b fooMAC -B 20 /tmp/HTC

So far, so good, now I can browse the content on the phone.

But, I can virtually do no file operation. If I try to copy a file to
the phone, nothing happens. The cp command is aborted without error
message after a fraction of a second.

When I now do a ls -l to see if the file was copied, the ls command
stalls. I even cannot umount the device with fusermount. I have to
disable bluetooth on the phone and have to enable it again.

When I use obexftp via Dolphin file manager on KDE4 the same thing, I
try to copy a file and nothing  happens, obexftp even disconnects the
phone from the computer.

Obexfs does not work much better, but it does not disconnect the phone
from the computer.

The only thing I can do is watch the folder content. I really would like
to have working file transfers.

Any hints welcome.

This is the software I use:

obexftp-0.23-20.1.x86_64
obexfs-0.11-90.1.x86_64
libopenobex1-1.5-26.1.x86_64

Linux kernel 3.7.10-1.16-desktop on openSUSE 12.3

Thanx
Malte

Re: [openobex-users] New releases: OpenOBEX-1.7 and ObexFTP-0.24

[Hendrik S. <po...@he...>]

Am 2013-03-05 22:22, schrieb Hendrik Sattler:
> Hi,
>
> this is the announcement for the release of OpenOBEX-1.7.
> You can download it either from my size at
> 
> 	http://www.hendrik-sattler.de/downloads/openobex/1.7/openobex-1.7-Source.tar.gz
> or from gitorious (generated file) at
> 	https://www.gitorious.org/openobex/mainline/archive-tarball/1.7
>
>
> Since ObexFTP (as available on github) doesn't work since
> OpenOBEX-1.6, this is also the
> announcement for ObexFTP-0.24 that works with OpenOBEX-1.7 (no, not
> with version 1.6).
> You can currently only download it from gitorious (generated file) at
> 	https://www.gitorious.org/obexftp/mainline/archive-tarball/0.24


These releases are now also available on Sourceforge:
http://sourceforge.net/projects/openobex/files/openobex/1.7/openobex-1.7-Source.tar.gz/download
http://sourceforge.net/projects/openobex/files/obexftp/0.24/obexftp-0.24-Source.tar.gz/download

Regards

Hendrik Sattler

[openobex-users] New releases: OpenOBEX-1.7 and ObexFTP-0.24

[Hendrik S. <po...@he...>]

Hi,

this is the announcement for the release of OpenOBEX-1.7.
You can download it either from my size at
	http://www.hendrik-sattler.de/downloads/openobex/1.7/openobex-1.7-Source.tar.gz
or from gitorious (generated file) at
	https://www.gitorious.org/openobex/mainline/archive-tarball/1.7


Since ObexFTP (as available on github) doesn't work since OpenOBEX-1.6, this is also the
announcement for ObexFTP-0.24 that works with OpenOBEX-1.7 (no, not with version 1.6).
You can currently only download it from gitorious (generated file) at
	https://www.gitorious.org/obexftp/mainline/archive-tarball/0.24


Regards,

Hendrik Sattler

Re: [openobex-users] Your patches for OpenOBEX

[Tomas H. <th...@re...>]

----- Original Message -----
> 
> 
> Tomas Hozza <th...@re...> schrieb:
> 
> >----- Original Message -----
> >> Hi,
> >> 
> >> I updated your bug tracking item of SourceForge:
> >>
> >https://sourceforge.net/tracker/index.php?func=detail&aid=3593585&group_id=8960&atid=108960
> >
> >I replied on SourceForge before noticing you wrote me directly.
> >
> >> Can you re-run the coverity script, so I can all problems can be
> >> fixed for latest git and I can release openobex-1.7?
> >
> >I will for sure do this and send you the error log.
> >
> >I would also like to update openOBEX in Fedora to the latest
> >version,
> >but there is still an issue with obexftp we are shipping (version
> >0.23).
> >Would it be possible to release also updated obexftp together with
> >openOBEX?
> >
> >Thanks.
> >
> >Regards,
> >Tomas Hozza
> 
> Hi Thomas,
> 
> I already prepared an updated version. The repository is at
> gitorious.org/obexftp. I also merged obexfs into it. There will be a
> new version once openobex 1.7 got released.
> 
> Regards,
> 
> HS

Great to hear that. I finished packaging the newest openobex git snapshot
for fedora and scanned it with Coverity (6.5.1). I used git repo snapshot
from 2013-02-26. Scan log is attached. Anyway if you would be interested
in scanning openobex (or other open-source projects) with Coverity you can
check http://scan.coverity.com/. Coverity is offering this for free
to open-source projects.

I'm sending you scan log ASAP because I would be more than happy to see
new version of openobex (and dependent projects like obexftp) released.
If you like I can help you with writing patches for those errors.

We also have two patches in Fedora that are not included in upstream git.
I'm not sure if previous openobex Fedora maintainer didn't send them
therefore I'll rebase them on the latest git commit and send them to you
ASAP.

Regards,

Tomas Hozza

Re: [openobex-users] debug output question

[Hendrik S. <po...@he...>]

Am Freitag, 27. Juli 2012, 01:20:46 schrieb Ray Hunter:
> Hendrik,
> 
> Here is what I get now:
> 
> /usr/local/obexftp-0.23/bin/obexftp -v -b 00:19:88:01:63:28 -B3 -c
> PDF_FILES -g test.pdf -o test.pdf
> obexftp_open()
> obexftp_connect_src()
> Connecting...obexftp_connect_src() BT 1
> cli_sync_request()
> Tx: 80 00 1A 10 00 04 00 46 00 13 F9 EC 7B C4 95 3C 11 D2 98 4E 52 54
> 00 DC 9E 09
> \obexftp_sync()
> client_done()
> client_done() Sender identified
> client_done() Found connection number: 136
> obexftp_sync() OBEX_HandleInput = 31
> obexftp_sync() Done success=1
> done
> Tried to connect for 402ms
> obexftp_setpath() Changing to PDF_FILES
> Sending "PDF_FILES"... obexftp_setpath() Setpath "PDF_FILES"
> cli_sync_request()
> Tx: 85 00 21 02 00 CB 00 00 00 88 01 00 17 00 50 00 44 00 46 00 5F 00
> 46 00 49 00
> Tx: 4C 00 45 00 53 00 00
> 
> |obexftp_sync()
> 
> client_done()
> obexftp_sync() OBEX_HandleInput = 3
> obexftp_sync() Done success=1
> done
> Receiving "test.pdf"... obexftp_get_type() Getting test.pdf -> test.pdf
> ((null)) cli_sync_request()
> Tx: 83 00 1D CB 00 00 00 88 01 00 15 00 74 00 65 00 73 00 74 00 2E 00
> 70 00 64 00
> Tx: 66 00 00
> /obexftp_sync()
> obexftp_sync() OBEX_HandleInput = 667
> Tx: 83 00 03
> -obexftp_sync() OBEX_HandleInput = 1024
> cli_obex_event() OBEX_EV_REQDONE: obex_rsp=53
> client_done()
> obexftp_sync() OBEX_HandleInput = 3
> obexftp_sync() Done success=0
> failed: test.pdf
> obexftp_disconnect()
> Disconnecting...cli_sync_request()
> Tx: 81 00 08 CB 00 00 00 88
> \obexftp_sync()
> client_done()
> obexftp_sync() OBEX_HandleInput = 3
> obexftp_sync() Done success=1
> done
> obexftp_close()
> 
> 
> I have the env set for debug and dump, but I dont see Rx output. I do
> see that I am getting obex_rsp=53 as part of the output. Is there
> something that I am missing here.

Ok, I'm sorry. This was only included after openobex1.5. So you have to 
recompile openobex to include RX dump output or use the latest greatest of  
both from
	gitorious.org/openobex
and
	gitorious.org/obexftp

BTW: It won't actually help you getting that file, just better information.

HS

Re: [openobex-users] debug output question

[Ray H. <ray...@ve...>]

Hendrik,

Here is what I get now:

/usr/local/obexftp-0.23/bin/obexftp -v -b 00:19:88:01:63:28 -B3 -c
PDF_FILES -g test.pdf -o test.pdf
obexftp_open()
obexftp_connect_src()
Connecting...obexftp_connect_src() BT 1
cli_sync_request()
Tx: 80 00 1A 10 00 04 00 46 00 13 F9 EC 7B C4 95 3C 11 D2 98 4E 52 54
00 DC 9E 09
\obexftp_sync()
client_done()
client_done() Sender identified
client_done() Found connection number: 136
obexftp_sync() OBEX_HandleInput = 31
obexftp_sync() Done success=1
done
Tried to connect for 402ms
obexftp_setpath() Changing to PDF_FILES
Sending "PDF_FILES"... obexftp_setpath() Setpath "PDF_FILES"
cli_sync_request()
Tx: 85 00 21 02 00 CB 00 00 00 88 01 00 17 00 50 00 44 00 46 00 5F 00
46 00 49 00
Tx: 4C 00 45 00 53 00 00
|obexftp_sync()
client_done()
obexftp_sync() OBEX_HandleInput = 3
obexftp_sync() Done success=1
done
Receiving "test.pdf"... obexftp_get_type() Getting test.pdf -> test.pdf ((null))
cli_sync_request()
Tx: 83 00 1D CB 00 00 00 88 01 00 15 00 74 00 65 00 73 00 74 00 2E 00
70 00 64 00
Tx: 66 00 00
/obexftp_sync()
obexftp_sync() OBEX_HandleInput = 667
Tx: 83 00 03
-obexftp_sync() OBEX_HandleInput = 1024
cli_obex_event() OBEX_EV_REQDONE: obex_rsp=53
client_done()
obexftp_sync() OBEX_HandleInput = 3
obexftp_sync() Done success=0
failed: test.pdf
obexftp_disconnect()
Disconnecting...cli_sync_request()
Tx: 81 00 08 CB 00 00 00 88
\obexftp_sync()
client_done()
obexftp_sync() OBEX_HandleInput = 3
obexftp_sync() Done success=1
done
obexftp_close()


I have the env set for debug and dump, but I dont see Rx output. I do
see that I am getting obex_rsp=53 as part of the output. Is there
something that I am missing here.


Thanks,
--
Ray


On Thu, Jul 26, 2012 at 1:36 PM, Hendrik Sattler
<po...@he...> wrote:
> Am Donnerstag, 26. Juli 2012, 17:02:53 schrieb Ray Hunter:
>> I am trying to find out why transferring a file that is a 2mb pdf file
>> fails, but I am not having much success. I am wondering if anyone
>> might point me in the right direction of why it would be failing and
>> if there is something that I can do:
>>
>> ObexFTP 0.23
>> OpenObex 1.3
>> device: Intermec CK32
>
> Can you upgrade to OpenObex 1.5 (not 1.6)? Because then...
>
> [...]
>> Receiving "CK32_User_Manual.pdf"... obexftp_get_type() Getting
>> CK32_User_Manual.pdf -> CK32_User_Manual.pdf ((null))
>> cli_sync_request()
>> Tx: 83 00 35 CB 00 00 00 4E 01 00 2D 00 43 00 4B 00 33 00 32 00 5F 00
>> 55 00 73 00
>> Tx: 65 00 72 00 5F 00 4D 00 61 00 6E 00 75 00 61 00 6C 00 2E 00 70 00
>> 64 00 66 00
>> Tx: 00
>> obexftp_sync()
>> obexftp_sync() OBEX_HandleInput = 667
>> Tx: 83 00 03
>> \obexftp_sync() OBEX_HandleInput = 1024
>> cli_obex_event() OBEX_EV_REQDONE: obex_rsp=50
>> client_done()
>> obexftp_sync() OBEX_HandleInput = 3
>> obexftp_sync() Done success=0
>> failed: CK32_User_Manual.pdf
>> obexftp_disconnect()
>> Disconnecting...cli_sync_request()
>> Tx: 81 00 08 CB 00 00 00 4E
>> obexftp_sync()
>> client_done()
>> obexftp_sync() OBEX_HandleInput = 3
>> obexftp_sync() Done success=1
>> done
>> obexftp_close()
>
> ...you can set environment variables for debugging without recompiling:
> OBEX_DEBUG=4
> OBEX_DUMP=3
>
> The latter is to also get the "Rx:" output from the device, not only just what
> is sent to the device (Tx).
>
> Btw: obex_rsp=50 meanst "Internal Server Error".
> That can mean almost anything.
>
> HS
>

Re: [openobex-users] debug output question

[Hendrik S. <po...@he...>]

Am Donnerstag, 26. Juli 2012, 17:02:53 schrieb Ray Hunter:
> I am trying to find out why transferring a file that is a 2mb pdf file
> fails, but I am not having much success. I am wondering if anyone
> might point me in the right direction of why it would be failing and
> if there is something that I can do:
> 
> ObexFTP 0.23
> OpenObex 1.3
> device: Intermec CK32

Can you upgrade to OpenObex 1.5 (not 1.6)? Because then...

[...]
> Receiving "CK32_User_Manual.pdf"... obexftp_get_type() Getting
> CK32_User_Manual.pdf -> CK32_User_Manual.pdf ((null))
> cli_sync_request()
> Tx: 83 00 35 CB 00 00 00 4E 01 00 2D 00 43 00 4B 00 33 00 32 00 5F 00
> 55 00 73 00
> Tx: 65 00 72 00 5F 00 4D 00 61 00 6E 00 75 00 61 00 6C 00 2E 00 70 00
> 64 00 66 00
> Tx: 00
> obexftp_sync()
> obexftp_sync() OBEX_HandleInput = 667
> Tx: 83 00 03
> \obexftp_sync() OBEX_HandleInput = 1024
> cli_obex_event() OBEX_EV_REQDONE: obex_rsp=50
> client_done()
> obexftp_sync() OBEX_HandleInput = 3
> obexftp_sync() Done success=0
> failed: CK32_User_Manual.pdf
> obexftp_disconnect()
> Disconnecting...cli_sync_request()
> Tx: 81 00 08 CB 00 00 00 4E
> obexftp_sync()
> client_done()
> obexftp_sync() OBEX_HandleInput = 3
> obexftp_sync() Done success=1
> done
> obexftp_close()

...you can set environment variables for debugging without recompiling:
OBEX_DEBUG=4
OBEX_DUMP=3

The latter is to also get the "Rx:" output from the device, not only just what 
is sent to the device (Tx).

Btw: obex_rsp=50 meanst "Internal Server Error".
That can mean almost anything.

HS

[openobex-users] debug output question

[Ray H. <ray...@ve...>]

I am trying to find out why transferring a file that is a 2mb pdf file
fails, but I am not having much success. I am wondering if anyone
might point me in the right direction of why it would be failing and
if there is something that I can do:

ObexFTP 0.23
OpenObex 1.3
device: Intermec CK32


Here is the output of the debug:

obexftp -b 00:19:88:01:63:28 -B3 -c PDF_FILES -g CK32_User_Manual.pdf
Connecting..\done
Tried to connect for 133ms
Sending "PDF_FILES"...|done
Receiving "CK32_User_Manual.pdf"...-failed: CK32_User_Manual.pdf
Disconnecting..\done

Here is the command now with debugging or verbose turned on:
/usr/local/obexftp-0.23/bin/obexftp -v -b 00:19:88:01:63:28 -B3 -c
PDF_FILES -g CK32_User_Manual.pdf
obexftp_open()
obexftp_connect_src()
Connecting...obexftp_connect_src() BT 1
cli_sync_request()
Tx: 80 00 1A 10 00 04 00 46 00 13 F9 EC 7B C4 95 3C 11 D2 98 4E 52 54
00 DC 9E 09
obexftp_sync()
client_done()
client_done() Sender identified
client_done() Found connection number: 78
obexftp_sync() OBEX_HandleInput = 31
obexftp_sync() Done success=1
done
Tried to connect for 415ms
obexftp_setpath() Changing to PDF_FILES
Sending "PDF_FILES"... obexftp_setpath() Setpath "PDF_FILES"
cli_sync_request()
Tx: 85 00 21 02 00 CB 00 00 00 4E 01 00 17 00 50 00 44 00 46 00 5F 00
46 00 49 00
Tx: 4C 00 45 00 53 00 00
obexftp_sync()
client_done()
obexftp_sync() OBEX_HandleInput = 3
obexftp_sync() Done success=1
done
Receiving "CK32_User_Manual.pdf"... obexftp_get_type() Getting
CK32_User_Manual.pdf -> CK32_User_Manual.pdf ((null))
cli_sync_request()
Tx: 83 00 35 CB 00 00 00 4E 01 00 2D 00 43 00 4B 00 33 00 32 00 5F 00
55 00 73 00
Tx: 65 00 72 00 5F 00 4D 00 61 00 6E 00 75 00 61 00 6C 00 2E 00 70 00
64 00 66 00
Tx: 00
obexftp_sync()
obexftp_sync() OBEX_HandleInput = 667
Tx: 83 00 03
\obexftp_sync() OBEX_HandleInput = 1024
cli_obex_event() OBEX_EV_REQDONE: obex_rsp=50
client_done()
obexftp_sync() OBEX_HandleInput = 3
obexftp_sync() Done success=0
failed: CK32_User_Manual.pdf
obexftp_disconnect()
Disconnecting...cli_sync_request()
Tx: 81 00 08 CB 00 00 00 4E
obexftp_sync()
client_done()
obexftp_sync() OBEX_HandleInput = 3
obexftp_sync() Done success=1
done
obexftp_close()

Re: [openobex-users] status of OpenOBEX?

[Hendrik S. <po...@he...>]

Iain Hibbert <pl...@ry...> schrieb:
>btw the CMake build does not have any 'maintainer-clean' target to tidy
>up

It doesn't because you are supposed to build in a separate build tree that you can clean up with rm -rf. The source tree stays clean. The autotools do need it due to the source tree pollution by autoreconf.

I.e.will tag version 1.6 this evening. I will also add a separate download directory on my server.

HS

Re: [openobex-users] status of OpenOBEX?

[Iain H. <pl...@ry...>]

On Mon, 19 Mar 2012, Hendrik Sattler wrote:

> Hi Iain,
>
> Am Montag, 19. März 2012, 10:33:43 schrieb Iain Hibbert:
> > No time to investigate further just now can look at it later, but NetBSD
> > has SOCK_CLOEXEC but not accept4() .. we have a paccept(2) instead which
> > also takes a sigmask, like so:
>
> I updated the master tree to add paccept() support. Please check if it
> compiles.

Yes thats fine (with autoconf and cmake both) and seems to be working ok
on NetBSD so far with obexapp.

btw the CMake build does not have any 'maintainer-clean' target to tidy up

iain

Re: [openobex-users] status of OpenOBEX?

[Hendrik S. <po...@he...>]

Hi Iain,

Am Montag, 19. März 2012, 10:33:43 schrieb Iain Hibbert:
> No time to investigate further just now can look at it later, but NetBSD
> has SOCK_CLOEXEC but not accept4() .. we have a paccept(2) instead which
> also takes a sigmask, like so:

I updated the master tree to add paccept() support. Please check if it 
compiles.

Thanks,

HS

Re: [openobex-users] status of OpenOBEX?

[hendrik <he...@lo...>]

Hi Iain,

Am 2012-03-19 10:33, schrieb Iain Hibbert:
> On Sun, 18 Mar 2012, Hendrik Sattler wrote:
>> Am Mittwoch, 14. März 2012, 15:44:01 schrieb Iain Hibbert:
>> > To be honest, any new release (1.6?) with the current changes 
>> would be
>> > welcomed
>> >
>> > As to the API, then yes I do agree that there are some problems. I 
>> would
>> > not choose to use openobex if I were to write an OBEX program, not 
>> least
>> > because the documentation is minimal. I have worked on software 
>> using
>> > openobex and found that it was really difficult to work with. 
>> However, I
>> > don't really have any better ideas :)
>>
>> For a start, I submitted some additional patches to my master 
>> branch.
>> Can you check them out and do some compile and runtime tests for 
>> your BSDs?
>> If everything goes well, the current state will be version 1.6.
>>
>> I compile tested it on Linux, Windows cross-compiled on Linux and 
>> Windows.
>
> No time to investigate further just now can look at it later, but 
> NetBSD
> has SOCK_CLOEXEC but not accept4() .. we have a paccept(2) instead 
> which
> also takes a sigmask, like so:
>
> int paccept(int s, struct sockaddr * restrict addr, socklen t *
> restrict addrlen, const sigset t * restrict sigmask, int flags);
>
> You could do some autoconfig detection for this but its probably just
> simpler to use fcntl all the time..  I mean, the overhead of the 
> extra
> syscall is not likely to be significant in this environment, is it?

In a multi-threaded environment, it is useful to not leak file 
descriptors. fcntl() helps but is not race-free without a lot of hassle.
The non-blocking-io flag (in a non-included later patch) doesn't have 
this problem.

> I don't think any of the other BSDs have SOCK_CLOEXEC or accept4() or
> paccept() so that shouldn't be a problem for them

I will add paccept() support. NetBSD is easily detected using
http://sourceforge.net/apps/mediawiki/predef/index.php?title=Operating_Systems#NetBSD
and I add an accept4() function wrapper:

#if defined(SOCK_CLOEXEC) && defined(__NetBSD__)
static __inline int accept4(int s, struct sockaddr * addr, socklen t 
*addrlen, int flags) {
     return paccept(s, addr, addrlen, NULL, flags);
}
#endif

It seems that SOCK_CLOEXEC and paccept() appeared at the same time 
(NetBSD 6.0), so this should be sufficiently safe.

Thanks for the hint :-)

Regards,

HS

Re: [openobex-users] status of OpenOBEX?

[Iain H. <pl...@ry...>]

On Sun, 18 Mar 2012, Hendrik Sattler wrote:

> Hi Iain,
>
> Am Mittwoch, 14. März 2012, 15:44:01 schrieb Iain Hibbert:
> > To be honest, any new release (1.6?) with the current changes would be
> > welcomed
> >
> > As to the API, then yes I do agree that there are some problems. I would
> > not choose to use openobex if I were to write an OBEX program, not least
> > because the documentation is minimal. I have worked on software using
> > openobex and found that it was really difficult to work with. However, I
> > don't really have any better ideas :)
>
> For a start, I submitted some additional patches to my master branch.
> Can you check them out and do some compile and runtime tests for your BSDs?
> If everything goes well, the current state will be version 1.6.
>
> I compile tested it on Linux, Windows cross-compiled on Linux and Windows.

No time to investigate further just now can look at it later, but NetBSD
has SOCK_CLOEXEC but not accept4() .. we have a paccept(2) instead which
also takes a sigmask, like so:

int paccept(int s, struct sockaddr * restrict addr, socklen t * restrict addrlen, const sigset t * restrict sigmask, int flags);

You could do some autoconfig detection for this but its probably just
simpler to use fcntl all the time..  I mean, the overhead of the extra
syscall is not likely to be significant in this environment, is it?

I don't think any of the other BSDs have SOCK_CLOEXEC or accept4() or
paccept() so that shouldn't be a problem for them

iain

Re: [openobex-users] status of OpenOBEX?

[Hendrik S. <po...@he...>]

Hi Iain,

Am Mittwoch, 14. März 2012, 15:44:01 schrieb Iain Hibbert:
> To be honest, any new release (1.6?) with the current changes would be
> welcomed
> 
> As to the API, then yes I do agree that there are some problems. I would
> not choose to use openobex if I were to write an OBEX program, not least
> because the documentation is minimal. I have worked on software using
> openobex and found that it was really difficult to work with. However, I
> don't really have any better ideas :)

For a start, I submitted some additional patches to my master branch.
Can you check them out and do some compile and runtime tests for your BSDs?
If everything goes well, the current state will be version 1.6.

I compile tested it on Linux, Windows cross-compiled on Linux and Windows.

HS
 

Re: [openobex-users] status of OpenOBEX?

[Hendrik S. <po...@he...>]

Am Mittwoch, 14. März 2012, 15:44:01 schrieb Iain Hibbert:
> On Sun, 11 Mar 2012, Hendrik Sattler wrote:
> > > Is anybody still interested in openobex?  I recall rumours of a 2.0
> > > release..
> > 
> > I am.
> 
> Well, since Hendrik is the main interested party perhaps Marcel could be
> convinced to transfer (or redirect) his domain to the gitorius page that
> Hendrik maintains?  Either that or just call the openobex project defunct
> and fork it with a new name..

I think I will keep the name in any case...

> > However, it is also obvious that openobex has some problems. I will
> > address those before releasing 2.0. This will include API changes. I
> > don't know, yet, if compatibility with 1.5 will be kept.
> 
> To be honest, any new release (1.6?) with the current changes would be
> welcomed

Ok, I will tag the current master branch on Gitorious.

> As to the API, then yes I do agree that there are some problems. I would
> not choose to use openobex if I were to write an OBEX program, not least
> because the documentation is minimal. I have worked on software using
> openobex and found that it was really difficult to work with. However, I
> don't really have any better ideas :)

An updated API will be easier to understand and a bit more object oriented (I 
plan on writing a C++ wrapper).

HS

Re: [openobex-users] status of OpenOBEX?

[Iain H. <pl...@ry...>]

On Sun, 11 Mar 2012, Hendrik Sattler wrote:

> > Is anybody still interested in openobex?  I recall rumours of a 2.0
> > release..
>
> I am.

Well, since Hendrik is the main interested party perhaps Marcel could be
convinced to transfer (or redirect) his domain to the gitorius page that
Hendrik maintains?  Either that or just call the openobex project defunct
and fork it with a new name..

> However, it is also obvious that openobex has some problems. I will address
> those before releasing 2.0. This will include API changes. I don't know, yet,
> if compatibility with 1.5 will be kept.

To be honest, any new release (1.6?) with the current changes would be
welcomed

As to the API, then yes I do agree that there are some problems. I would
not choose to use openobex if I were to write an OBEX program, not least
because the documentation is minimal. I have worked on software using
openobex and found that it was really difficult to work with. However, I
don't really have any better ideas :)

iain

Re: [openobex-users] status of OpenOBEX?

[Christian Z. <za...@tr...>]

Hendrik,

Am 11.03.2012 um 11:10 schrieb Hendrik Sattler:

>> The www.openobex.org pages are
> 
> ...still there but will probably never be updated.
> I could host that site on my server but Marcel is owner of this domain.

I'm hosting the Trac and Marcel's domain forwards there. I though about dropping it for something more suitable - ideas welcome. Maybe some simple blog package to get information out more quickly?


thanks,
Christian





Grüße,
Christian

Re: [openobex-users] status of OpenOBEX?

[Hendrik S. <po...@he...>]

Hi Iain,

Am Freitag, 9. März 2012, 20:57:48 schrieb Iain Hibbert:
> I wonder, what is the status of openobex now?
> 
> I see that the code repository at git.kernel.org was never reinstated,
> though the project is present and owned by Marcel Holtmann. Then, the
> distribution files are no longer available in the www.kernel.org
> directory. Neither have any recent releases made it to the sourceforge
> hosting site, and the source is no longer at sourceforge. The
> www.openobex.org pages are

...still there but will probably never be updated.
I could host that site on my server but Marcel is owner of this domain.


> If I recall, the BlueZ folks have essentially moved on and are focusing on
> obexd which handles this directly instead of using openobex, and patches
> posted here never seemed to make it into any repository except the
> unofficial http://gitorious.org/openobex maintained by Hendrik Sattler.
> 
> Is anybody still interested in openobex?  I recall rumours of a 2.0
> release..

I am. Obexd is a bluez plugin and bluetooth is its focus is (and the current 
main usage of the OBEX protocol).

However, it is also obvious that openobex has some problems. I will address 
those before releasing 2.0. This will include API changes. I don't know, yet, 
if compatibility with 1.5 will be kept.

Regards,

HS

[openobex-users] status of OpenOBEX?

[Iain H. <pl...@ry...>]

Hi

I wonder, what is the status of openobex now?

I see that the code repository at git.kernel.org was never reinstated,
though the project is present and owned by Marcel Holtmann. Then, the
distribution files are no longer available in the www.kernel.org
directory. Neither have any recent releases made it to the sourceforge
hosting site, and the source is no longer at sourceforge. The
www.openobex.org pages are

If I recall, the BlueZ folks have essentially moved on and are focusing on
obexd which handles this directly instead of using openobex, and patches
posted here never seemed to make it into any repository except the
unofficial http://gitorious.org/openobex maintained by Hendrik Sattler.

Is anybody still interested in openobex?  I recall rumours of a 2.0
release..

regards,
iain