Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Andrew Radke <andrew@radke.iig.com.au>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez and OBEX File Transfer
Date: 31 Jul 2003 00:43:02 +0200	[thread overview]
Message-ID: <1059605011.1832.40.camel@pegasus> (raw)
In-Reply-To: <3F26FB4B.6060007@radke.iig.com.au>

Hi Andrew,

> > I have started a btftp client, which you can found in the BlueZ CVS in
> > the repository obex. But at the moment no btftpd exists.
> 
> The client will be a nice addition. Any plans on the btftpd? Anything a 
> non-programmer can do to help? Write it in Perl maybe? :-)

I don't have the time nor the money to work fulltime on it, so don't
expect anything very soon.

And I never read anything about a Bluetooth Perl binding, but it is
socket programming, so maybe it is already possible. But I code in C, so
why should I use Perl ;)

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2003-07-30 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26 14:37 [Bluez-users] bluez and OBEX File Transfer Andrew Radke
2003-07-28  8:16 ` Marcel Holtmann
2003-07-29 22:55   ` Andrew Radke
2003-07-30 22:43     ` Marcel Holtmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1059605011.1832.40.camel@pegasus \
    --to=marcel@rvs.uni-bielefeld.de \
    --cc=andrew@radke.iig.com.au \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox