mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Gang Yan <yangang@kylinos.cn>
Subject: Re: [PATCH mptcp-next 5/7] Add MPTCP support to ServerSocket class
Date: Thu, 31 Jul 2025 00:05:01 +0200	[thread overview]
Message-ID: <6c890c6c-fa91-4310-b07d-fa7207341aae@kernel.org> (raw)
In-Reply-To: <f5c39ac151fc97dd3625f5a48398716a483794d2.1753247666.git.geliang@kernel.org>

Hi Geliang,

On 23/07/2025 07:16, Geliang Tang wrote:
> This patch extends ServerSocket to support Multipath TCP (MPTCP) by:
> 
> 1. Adding a new constructor that accepts an mptcp parameter to enable
>    MPTCP
> 2. Introducing a new createImpl factory method that propagates the MPTCP
>    setting to the underlying socket implementation
> 3. Maintaining all existing functionality while adding MPTCP capabilities
> 
> The new constructor follows the same pattern as existing ServerSocket
> constructors but adds the mptcp parameter to control protocol selection.
> When enabled, the implementation uses the MPTCP-enabled socket creation
> path established in previous patches.

Similar to my comment in patch 2/7, I don't know what is best in this
project, but maybe instead of duplicating helpers, you could have the
previous helper calling the new extension?

So ServerSocket(int port, int backlog, InetAddress bindAddr) would call
the new one with 'mptcp' as new parameter? Same for createImpl()?

But not sure what the Java maintainers prefer. Maybe they are OK with
what you suggested.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2025-07-30 22:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23  5:16 [PATCH mptcp-next 0/7] Add MPTCP support to Java Networking API Geliang Tang
2025-07-23  5:16 ` [PATCH mptcp-next 1/7] Add MPTCP support for socket creation Geliang Tang
2025-07-30 22:03   ` Matthieu Baerts
2025-07-23  5:16 ` [PATCH mptcp-next 2/7] Add MPTCP server socket creation support Geliang Tang
2025-07-30 22:04   ` Matthieu Baerts
2025-07-23  5:16 ` [PATCH mptcp-next 3/7] Add MPTCP client " Geliang Tang
2025-07-23  5:16 ` [PATCH mptcp-next 4/7] Add MPTCP support to NioSocketImpl Geliang Tang
2025-07-23  5:16 ` [PATCH mptcp-next 5/7] Add MPTCP support to ServerSocket class Geliang Tang
2025-07-30 22:05   ` Matthieu Baerts [this message]
2025-07-23  5:16 ` [PATCH mptcp-next 6/7] Add MPTCP support to Socket class Geliang Tang
2025-07-30 22:05   ` Matthieu Baerts
2025-07-23  5:16 ` [PATCH mptcp-next 7/7] Add test cases for MPTCP socket functionality Geliang Tang
2025-07-30 22:08   ` Matthieu Baerts
2025-07-30 22:03 ` [PATCH mptcp-next 0/7] Add MPTCP support to Java Networking API Matthieu Baerts
2025-07-31  7:49   ` Geliang Tang
2025-07-31  9:33     ` Matthieu Baerts

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=6c890c6c-fa91-4310-b07d-fa7207341aae@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=yangang@kylinos.cn \
    /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).