From: Dave Platt <dplatt@radagast.org>
To: linux-hams@vger.kernel.org
Subject: Re: AX.25 Kernel - problem - ax25_sendmsg returns EMSGSIZE !
Date: Mon, 08 Oct 2007 17:59:31 -0700 [thread overview]
Message-ID: <470AD273.40007@radagast.org> (raw)
In-Reply-To: <470ACEA0.1080307@dimebank.com>
Chris Kantarjiev wrote:
>
>> That's why I'd favor using SOCK_STREAM for AX.25 connections (just
>> as TCP uses SOCK_STREAM) - there's no requirement with SOCK_STREAM
>> that the sender and receiver coordinate on the size of the largest
>> write operation. This would seem to ease the software compatibility
>> problem quite a bit!
>
> But TCP is a reliable stream, without internal record delimeters.
> SOCK_SEQPACKET is meant to retain the record delimiters and make them
> visible to the endpoints.
>
> So it depends entirely on what the application level is trying to do.
Quite right! I think that there are plenty of places for both
sorts of protocols.
I do think that having SOCK_STREAM available for AX.25 would be a good
idea. It would make it easier for TCP-based applications to be ported
over to AX.25.
next prev parent reply other threads:[~2007-10-09 0:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 19:58 AX.25 Kernel - problem - ax25_sendmsg returns EMSGSIZE ! Tihomir Heidelberg - 9a4gl
2007-10-08 8:29 ` Hamish Moffatt
2007-10-08 11:10 ` Tihomir Heidelberg - 9a4gl
2007-10-08 13:44 ` Hamish Moffatt
2007-10-08 14:53 ` Tihomir Heidelberg - 9a4gl
2007-10-08 15:51 ` Dave Platt
2007-10-08 19:38 ` Tihomir Heidelberg - 9a4gl
2007-10-08 22:36 ` Hamish Moffatt
2007-10-08 23:10 ` Dave Platt
2007-10-09 0:43 ` Chris Kantarjiev
2007-10-09 0:59 ` Dave Platt [this message]
2007-10-09 6:47 ` Tihomir Heidelberg - 9a4gl
2008-02-12 10:40 ` [BUG] [AX25] in libax25 Bernard Pidoux F6BVP
2008-02-12 11:20 ` Matti Aarnio
2007-10-08 8:41 ` AX.25 Kernel - problem - ax25_sendmsg returns EMSGSIZE ! Hamish Moffatt
2007-10-08 10:45 ` Ralf Baechle DL5RB
2007-10-08 12:25 ` Tihomir Heidelberg - 9a4gl
2007-10-08 16:55 ` Stephen Hemminger
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=470AD273.40007@radagast.org \
--to=dplatt@radagast.org \
--cc=linux-hams@vger.kernel.org \
/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