No need to use response methods returning a Future, if not used

[franz1981]

This is introducing a small, but noticeable performance improvement while interacting with `WriteStream', both saving few object allocations and useless work to happen.

Existing end methods return Future, that mean adding Netty listeners and creating wrapping Futures: given that are not used, we can get rid of them by passing null; not very elegant but it works

[franz1981]

@tsegismont Any chance we could expose (on Vert-x) specific fire-and-forget methods instead of passing null?

[geoand]

Interesting, thanks!

[quarkus-bot]

Failing Jobs - Building 4881220

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: extensions/hibernate-search-orm-elasticsearch/deployment 
! Skipped: extensions/hibernate-search-orm-coordination-outbox-polling/deployment integration-tests/devmode integration-tests/hibernate-search-orm-elasticsearch and 3 more

📦 extensions/hibernate-search-orm-elasticsearch/deployment

✖ Failed to execute goal io.fabric8:docker-maven-plugin:0.39.1:start (docker-start) on project quarkus-hibernate-search-orm-elasticsearch-deployment: I/O Error

[tsegismont]

@tsegismont Any chance we could expose (on Vert-x) specific fire-and-forget methods instead of passing null?

Sorry no, we've chosen to have two programming models exposed: futurized and callbacks (which was the only one available in earlier versions).

The best way to proceed is what you did, I think: use a null callback.

[franz1981]

Thanks @tsegismont to confirm that what I've done is idiomatic with the existing API 👍