From: Mayank Batra <mayankbatra@yahoo.co.in>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] A small query
Date: Sun, 8 May 2005 13:44:00 +0100 (BST) [thread overview]
Message-ID: <20050508124400.70168.qmail@web8302.mail.in.yahoo.com> (raw)
In-Reply-To: 6667
Marcel,
> > Swapping message_type and packet_type makes no
> > difference to a2play but it makes a lot of
> difference
> > to a2recv.
>
> Why can this be? Doesn't a2play uses message_type
> and packet_type at
> all?
>
This is because a2play sends commands and not replies.
In commands the message_type is always 0 and
packet_type is also 0, thus it makes no difference
whether packet_type is before or after message_type.
But, in a2recv we have to send replies, and this is
when the trouble comes up. In replies, message_type is
whether the message was acceped or denied. But
packet_type is again 0. So here message_type is not
always 0. Thus interchanging them WILL create a mess
up.
Mayank
________________________________________________________________________
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-05-08 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 12:44 Mayank Batra [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-03 13:09 [Bluez-devel] A small query Mayank Batra
2005-05-03 15:38 ` Marcel Holtmann
2005-05-05 12:29 ` Mayank Batra
2005-05-05 13:13 ` 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=20050508124400.70168.qmail@web8302.mail.in.yahoo.com \
--to=mayankbatra@yahoo.co.in \
--cc=bluez-devel@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