linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arch Sayo <a12chi@yahoo.com>
To: Bluez-users@lists.sourceforge.net
Subject: [Bluez-users] 2 Successive OBEX Connect Request
Date: Tue, 29 Nov 2005 22:40:37 -0800 (PST)	[thread overview]
Message-ID: <20051130064037.90802.qmail@web32412.mail.mud.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 456 bytes --]

Hi,
   
  I would like to ask the implications on BlueZ whenever a Bluetooth device issues 2 Successive OBEX Connect Requests. This was done without any OBEX Disconnect Request after the first Connect Request. This is how the new Samsung D600 phone is doing a Bluetooth transaction when you're doing a Bluetooth printing.
   
  Thank you.
  Arch Sayo

		
---------------------------------
 Yahoo! Music Unlimited - Access over 1 million songs. Try it free.

[-- Attachment #2: Type: text/html, Size: 608 bytes --]

             reply	other threads:[~2005-11-30  6:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30  6:40 Arch Sayo [this message]
2005-11-30  6:43 ` [Bluez-users] 2 Successive OBEX Connect Request Marcel Holtmann

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=20051130064037.90802.qmail@web32412.mail.mud.yahoo.com \
    --to=a12chi@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;
as well as URLs for NNTP newsgroup(s).