Renamed NettyId to NettySync

[Pask423]

closes #3625

[adamw]

Thanks!

@kciesielski @lbialy what do you think, how should we call the synchronouse variants of tapir interpreters / sttp client backends? For reference:

• they use the Id "effect" type
• in sttp client, we currently have e.g. DefaultSyncBackend, HttpClientSyncBackend
• for Futures, we have NettyFutureServer, HttpClientFutureBackend; for CE, NettyCatsServer, HttpClientCatsBackend
• hence here propose also NettySyncServer
• alternatively, we can go with simply NettyServer and HttpClientBackend

opinions? :)

[lbialy]

While NettyServer sounds good and reminds me of time ten years ago when you had SomethingServer and maybe, at most, an AsyncSomethingServer, we have so many variants now that lack of prefix is rather confusing instead of immediately understandable. Therefore my vote is on NettySyncServer because now, in Scala, given the amount of competing approaches, sync is just one option. I imagine with caprese/gears we'll have another variant with capability types annotations and it will also be sync so there's possible future ambiguity on "sync" term too :)

…

On Tue 16. Apr 2024 at 13:25, Adam Warski ***@***.***> wrote: Thanks! @kciesielski <https://github.com/kciesielski> @lbialy <https://github.com/lbialy> what do you think, how should we call the synchronouse variants of tapir interpreters / sttp client backends? For reference: - they use the Id "effect" type - in sttp client, we currently have e.g. DefaultSyncBackend, HttpClientSyncBackend - for Futures, we have NettyFutureServer, HttpClientFutureBackend; for CE, NettyCatsServer, HttpClientCatsBackend - hence here propose also NettySyncServer - alternatively, we can go with simply NettyServer and HttpClientBackend opinions? :) — Reply to this email directly, view it on GitHub <#3689 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACBVNUW7PFAJFRF3SC7HYLDY5UDEBAVCNFSM6AAAAABGJC5CVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJYHA2TSMBSG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[kciesielski]

+1 to @lbialy :)

[adamw]

Ok, thanks for your input :)