Stop doing initial data that way, it's a bad idea D:<

This commit is contained in:
Nadja Reitzenstein 2022-11-04 16:07:33 +01:00
parent b12fa851c5
commit a1ca3e2ccd

View File

@ -27,12 +27,11 @@ interface Bootstrap
mechanisms @2 () -> ( mechs :List(Text) ); mechanisms @2 () -> ( mechs :List(Text) );
# Get a list of Mechanisms this server allows in this context. # Get a list of Mechanisms this server allows in this context.
createSession @3 ( mechanism :Text, initialData :Data ) createSession @3 ( mechanism :Text ) -> ( authentication :Authentication );
-> ( authentication :Authentication );
# Create a new session with the server that you wish to authenticate using `mechanism`. If the # Create a new session with the server that you wish to authenticate using `mechanism`. If the
# mechanism is a client-first mechanism you MAY set `initialData` to contain the data you want # mechanism is a client-first mechanism you can then immediately call Authentication::step with
# to send. If the mechanism is server-first or you do not wish to send initial data, make # initial data in a pipelined fashion. If the mechanism is server-first you must call
# initialData a NULL-pointer. # Authentication::step with a NULL `data` parameter.
} }
struct Session { struct Session {