Linux bluetooth development
 help / color / mirror / Atom feed
From: "Thor Egil Skaug" <paxtonrd@hotmail.com>
To: steven.singer@csr.com
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] AUX1 packets
Date: Mon, 01 Mar 2004 09:02:36 -0800	[thread overview]
Message-ID: <BAY1-F9yDAGmbSTM5TP00003ee1@hotmail.com> (raw)

I am doing research on quality of service and fault tolerance in distributed 
systems,
and what I am working on is a configurable middleware with QoS 
(MicroQoSCORBA).
Currently I am researching meaningful QoS mechanisms for wireless 
transports, and right
now I am focusing on Bluetooth.

Middleware is supposed to mask all these things for the user (application 
designer),
including the different mechanisms for getting Bluetooth or whatever 
wireless or wired
transport to achieve the QoS that he/she expects.

So I am doing a lot of tests by playing around with the things you can do to 
make a BT connection
behave differently, to define a QoS space. In other wireless transports 
there are other switches
to play with. I am not necessarily looking to prove that a certain thing 
works, but also to prove
it doesn't.

What I wanted to do was let the middleware decide on the packet types for 
Bluetooth,
and since the same logic will be at both ends, both transports will choose 
the same packet
type as the link quality changes. Which makes sense since the time between a 
request is
sent from a client to a reply is sent from a server could be enough to have 
a decent change
in link quality.

Bringing me to the next question:

If I issue create_connection with a DH5 packet, the LM knows it can use DH5 
and DM1.
If I later issue change_conn_packet_type with DH3, is the LM allowed to 
switch to
DH5 behind my back if it wants to? Or is there a stored bit pattern in the 
LM of the
packet types that I allow that gets overwritten completely with the pattern 
in change_conn_pt?

I understand that the more meaningful thing to do is allowing all DH and DM 
packets, and let
the LM decide.

Thor

_________________________________________________________________
Click, drag and drop. My MSN is the simple way to design your homepage. 
http://click.atdmt.com/AVE/go/onm00200364ave/direct/01/



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2004-03-01 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01 17:02 Thor Egil Skaug [this message]
2004-03-01 18:13 ` [Bluez-users] AUX1 packets Steven Singer
2004-03-01 19:09   ` Thor Egil Skaug
  -- strict thread matches above, loose matches on Subject: below --
2004-02-28 19:35 Thor Egil Skaug
2004-03-01 14:55 ` Marcel Holtmann
2004-03-01 15:44   ` Thor Egil Skaug
2004-03-01 15:58     ` Steven Singer
2004-03-01 16:07       ` Thor Egil Skaug
2004-03-01 16:18         ` Steven Singer

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=BAY1-F9yDAGmbSTM5TP00003ee1@hotmail.com \
    --to=paxtonrd@hotmail.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=steven.singer@csr.com \
    /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