You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, everyone(maybe I should @vasilvv specially..), I read your demo code quic-transport.
But there are a little code makes me little confusion:
ifisinstance(event, StreamDataReceived) andevent.stream_id==2: // [+] @aself.client_indication_data+=event.dataifevent.end_stream:
self.process_client_indication()
ifself.is_closing_or_closed():
return# Pass all buffered events into the handler now that it's# available.foreinself.pending_events:
self.handler.quic_event_received(e)
self.pending_events.clear()
else:
# We have received some application data before we have the# request URL available, which is possible since there is no# ordering guarantee on data between different QUIC streams.# Buffer the data for now.self.pending_events.append(event)
at @A, we use a magic number which is 2, I have 3 question about this:
what does it means at here.
Why we should use 2 instead of 3, 4, 5, etc...
Which document or source code introduce this?
Thank u very much!
The text was updated successfully, but these errors were encountered:
In order to verify that the client's origin is allowed to connect to
the server in question, the user agent has to communicate the origin
to the server. This is accomplished by sending a special message,
called client indication, on stream 2, which is the first client-
initiated unidirectional stream.
Hello, everyone(maybe I should @vasilvv specially..), I read your demo code quic-transport.
But there are a little code makes me little confusion:
at @A, we use a magic number which is 2, I have 3 question about this:
Thank u very much!
The text was updated successfully, but these errors were encountered: