How should I deal with http/2 stream id in VERT.X HTTP/2 CLIENT?

[Nam]

The HTTP/2 specification describes stream id as follows:

Stream identifiers cannot be reused.

Long-lived connections can result in an endpoint exhausting the available range of stream identifiers.

A client that is unable to establish a new stream identifier can establish a new connection for new streams.  A server that is unable to establish a new stream identifier can send a GOAWAY frame so that the client is forced to open a new connection for new streams.

I am fascinated by vertx, and I am implementing and using http2 client and server.

I don't have much understanding and knowledge about http2 stream id.

In VERT.X, could it be that the stream id is exhausted causing the problem?

My program has a failover feature implemented in case there is a problem with the connection.

Nevertheless, is there any part that must be dealt with when using vert.x http2 client when a problem occurs due to stream id?

[Julien Viet]

Hi,

yes this is possible for a connection that would create 2^30 requests
in Vert.x, since Vert.x uses a monotonic sequence for allocating
stream identifiers.

In practice I doubt this ever happens, most TCP connections will be
closed before the sequence is exhausted.

If that would ever be a case (perhaps it would be at some point with
HTTP/3 or later), then Vert.x would implement a mechanism to alleviate
this.

So you should not worry about this and use the client safely.

Julien

> --
> You received this message because you are subscribed to the Google Groups "vert.x" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/b23bffc9-2c5d-4111-93ad-5eb27b118ff3n%40googlegroups.com.

[Nam]

It is really an honor for the project leader to respond directly.

I really fell in love with VERT.X

I am working hard as an evangelist.:)

I am Korean.

I developed an internal core network interworking module for 5G-based positioning technology based on VERT.X.

It is probably the first case of applying VERT.X among global companies in Korea.

5G SA is before commercialization, but is currently in service in 5G NSA mode.

I have a question.

Is there any problem with the above when keeping the CONNECTION-ORIENTED state with one connection?

The 5G specification released by 3GPP states that it should operate in the SINGLE CONNECTION & CONNECTION-ORIENTED method.

Once again, I would like to ask for your answer.

2021년 6월 2일 수요일 오전 12시 52분 25초 UTC+9에 jul...@julienviet.com님이 작성: