From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] L2CAP retransmission, flow control
Date: Wed, 09 Feb 2005 15:06:23 +0100 [thread overview]
Message-ID: <1107957983.13863.37.camel@pegasus> (raw)
In-Reply-To: <1107955473.9489.37.camel@mammoth.research.nokia.com>
Hi Imre,
> > If SOCK_STREAM is requested and RFC negotiation fails, then also the
> > connection must fail. For SOCK_STREAM you need flow control.
> >
> > For SOCK_DGRAM and SOCK_RAW we don't do anything. The SOCK_DGRAM is for
> > connection-less channels and SOCK_RAW gives access to the signal channel
> > itself.
> >
> > If you use SOCK_SEQPACKET (current type) and mode > 0 then negotiate RFC
> > and if success then use it, otherwise fail.
> >
>
> Shouldn't we support the flow control only mode, so without
> retransmission? For SOCK_SEQPACKET and a specific mode value for
> example.
if you select SOCK_SEQPACKET and set the mode to flow control and
retransmission then this must be negotiated and on success this can be
used.
For SOCK_STREAM only the flow control is really needed, but also having
retransmission whould be great.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-09 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 7:40 [Bluez-devel] L2CAP retransmission, flow control Imre Deak
2005-02-09 8:48 ` Marcel Holtmann
2005-02-09 9:22 ` Imre Deak
2005-02-09 10:18 ` Marcel Holtmann
2005-02-09 13:24 ` Imre Deak
2005-02-09 14:06 ` Marcel Holtmann [this message]
2005-02-09 17:04 ` Imre Deak
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=1107957983.13863.37.camel@pegasus \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.