Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Threading model (was Re: Jetty 12 schedule?_
  • From: "Cantor, Scott" <cantor.2@xxxxxxx>
  • Date: Mon, 14 Nov 2022 14:15:12 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 128.146.138.9) smtp.rcpttodomain=eclipse.org smtp.mailfrom=osu.edu; dmarc=pass (p=none sp=none pct=100) action=none header.from=osu.edu; dkim=pass (signature was verified) header.d=osu.edu; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=osu.edu] dkim=[1,1,header.d=osu.edu] dmarc=[1,1,header.from=osu.edu])
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=osu.edu; dmarc=pass action=none header.from=osu.edu; dkim=pass header.d=osu.edu; arc=none
  • Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=EGzf2oKOKUwupz3qh3qQ0YrCz6bFVQApJRIFAR2iseQ=; b=L/XKGiCry89T89/XrOf/WzVplovYFva1fcMRtZqheAZwKXFm3Yp+SWET6242BFoe7HHyxP+9DlegwC7U1bEBA5aupD2mv3zpgpeOe3L3NOVelSToca+6GBZzvgw2j2tuuty/QcfB0RDfpAfoiq4VPIhY1nXdX7HXz2SPP6q6ou+ffdNB8qlB8RE4xbDACMxcpku/9ZiFS4zRc2ukyUhCaLexlkekWhpsN/pQAEf/AjC40WM74E1/NB/1JnbAWafoWtbQTiEAraOe1nfLoHshd5HV7YXxlYpQx3nYITvQMeCagh3vMiyopl7uYNuhHUyvawI3G8X+P0zGrzQnpy3hBw==
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=EGzf2oKOKUwupz3qh3qQ0YrCz6bFVQApJRIFAR2iseQ=; b=bCzV3aFwqEgVX9d2CvPAtfWgvVTuNGIaPYiTqTaxfyGOgktcn/ePi6rGromBqytalW4aH5EFoMpRgTBItpn6A6TXrY+uM4xGpo6NFv7F3xQsZ+j/hAluGJtDDOXMsADTgiLeJjp0Sk1L9kMkDkBfcs/ysZXEOspuoJcfVjQ7W8r8dHg+UWOUqvbBdlfkfDOH2YcbvI+KEzAqgzAyHY9Q+b8nE+m6jtizhLy5qN6UVdjJ+E6cf7AWnCONLQpHYg8/HssiD9nPpWiJIFY8SA2Irp9A3qGaWgQEVgeVAZSRktnSNaHuxQ7jylAbbFeNhwOIGmSQ8MRRIun1YcDdbzwgyw==
  • Arc-seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=N+WS9yFSGysqCkEAqq7eSNeqLT/YwFabOVHnPoOlwnnh62NjhtqAdS1xYN6guGhbyB8o+BnfnkiKjxd3STH3kGj/wsVIK7uMKWAllftlreqo1EeN00rHsb4l4W9tDpmZPJtZxN1azo3Y9gBZ9yKzZNFwCPUx+5Z1JxD9ySqUBjfdYTCLNUkiZ8/uzZE0/ZAupgE/97AcO3TGN26sHCN3JRPyxmWnOKYEJsHZiNota3rGen0LivjN+UsZm2Zv5+/OYo2pbO/+JYsSY5DDLmHFz0aC9RbQFc7SJyngtF5TKhyn5ezRwP6oEpXX8BxBi8nUC7teDOIBjNgsTgMKXdKEsQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=V0D30eofh96jvIz8aq4y2yAjik8jlCZw12ik7rgEigO1olEmpAFM5E3HB01AxthcdKyqQZzJY62mcrpbwE5u/1zyQb/1QBUGCQb9pZzZ5EUKTcfXBrdvZmfWE4goTDOlmYs9HOJLlxZ5T4Nj+adOs3ujwO3ZhfiAP5Nb/cuB5wgHqFwfFkF4YtB7RNQuo/tZk8J67VCdKslJvmfmIKf72CAauekApk8wKwDSzVK5L6x5J6NOOMBWbukL2bTXlaXbCNny3X0qez6Jpz+S0HM5ySaYdCCQA3q2c6TphdrXRA3co2CeJ2Ix0KxCVYxroVCELqGMrG+ghK3Iz+sLaJUyEg==
  • Delivered-to: jetty-users@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/jetty-users/>
  • List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHY9J6Oj64MyBctz0SBYEVoDJxEIq43Cn4AgABezwCAAGB5gIAA+SwAgAVnAwA=
  • Thread-topic: [jetty-users] Threading model (was Re: Jetty 12 schedule?_
  • User-agent: Microsoft-MacOutlook/16.66.22102801
On 11/10/22, 5:45 PM, "jetty-users on behalf of Greg Wilkins" <jetty-users-bounces@xxxxxxxxxxx on behalf of gregw@xxxxxxxxxxx> wrote:

>    To my knowledge that cannot happen.... at least not with normal
> threads.   Perhaps in future with virtual threads, then threadlocals might
> be more of a problem, but their usage will be optional in Jetty.

Virtual threads don't change things if they're implemented the way they're supposed to be, they intended to maintain the existing contracts for threading in Java, and that includes thread-locals.

The whole point of that work in fact is to get people to stop coding up asynchronous designs, because multi-threading is a lot simpler. The async behaviors are supposed to be moved under the covers.

-- Scott

Back to the top