From: Lalith Chakravarthi <lalithvc@yahoo.com>
To: bluez-users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Simple file push, without OBEX?
Date: Thu, 1 Apr 2004 02:59:10 -0800 (PST) [thread overview]
Message-ID: <20040401105910.81075.qmail@web40713.mail.yahoo.com> (raw)
>
> Is it possible to send a simple file, such as a vCard, or an image,
> from a MIDlet running on one device to another device, via bluetooth?
>
> It seems to be an operation that requires an OBEX push to me, but as
> no handsets implement OBEX in their JSR-82 implementations, that
> leaves RFCOMM or L2CAP. As far as I can see, RFCOMM/L2CAP
> connections are always client/server. Is it possible to simply
> connect to another device and send a file using these methods,
> without specifying a service or custom MIDlet to connect to, and
> have the receiver deal with the file appropriately? Or is there a
> generic service that accepts incoming files, that can be specified
> in the connection string?
>
> thanks for any help. And no, this isn't an April Fools joke!
>
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-04-01 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 10:59 Lalith Chakravarthi [this message]
2004-04-01 11:55 ` [Bluez-users] Simple file push, without OBEX? Stephen Crane
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=20040401105910.81075.qmail@web40713.mail.yahoo.com \
--to=lalithvc@yahoo.com \
--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