From f23540bd24dd81de43a2cf1b8e1a99600cc918df Mon Sep 17 00:00:00 2001 From: James M Snell Date: Mon, 6 Nov 2023 14:14:18 +0000 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Dominik Picheta --- index.bs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.bs b/index.bs index 19f53ff..957fadc 100644 --- a/index.bs +++ b/index.bs @@ -43,7 +43,7 @@ A socket becomes closed when its {{close()}} method is called. A socket c

Connect

-

The [=connect=] method here is defined in a `sockets` module here only for initial implementation purposes. It is imagined that in a finalized standard definition, the [=connect=] would be exposed as a global or within a [=binding object=]

+

The [=connect=] method here is defined in a `sockets` module only for initial implementation purposes. It is imagined that in a finalized standard definition, the [=connect=] would be exposed as a global or within a [=binding object=]

A socket can be constructed using a connect method defined in a `sockets` module (early implementations may use `vendor:sockets` for the module name), or defined on a [=binding object=]. @@ -51,7 +51,7 @@ The connect method is the primary mechanism for creating a [=socket=] instance.

Binding Object

-

A [=binding object=] in this context is essentially just an object that exposes the a [=connect=] method conformant with this specification. It is anticipated that a runtime may have any number of such objects. This is an area where there is still active discussion on how this should be defined.

+

A [=binding object=] in this context is essentially just an object that exposes a [=connect=] method conformant with this specification. It is anticipated that a runtime may have any number of such objects. This is an area where there is still active discussion on how this should be defined.

The binding object defines extra socket `connect` options. The options it contains can modify the behaviour of the `connect` invoked on it. Some of the options it can define: