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
For the moment, all the services I wrote had the "Blocking" annotation.
It works pretty well, but its is not an ideal solution for an asynchronous framework like vertx.
It would be interesting to have a way of writing asynchronous methods, either with the Jax-RS 2.0 AsyncResponse (which is quite complex) or by letting the methods have a way of calling a "resume" method with the result as a parameter.
The text was updated successfully, but these errors were encountered:
I think this could be achieved using the Vert.X message bus system ... which I already plan to make easier to use with annotations ... combining those two you could achieve this.
If a REST method returns a Future than a handler waits for the future to finish ... and returns the desired response.
The writer is determined according the future.result() type ...
For the moment, all the services I wrote had the "Blocking" annotation.
It works pretty well, but its is not an ideal solution for an asynchronous framework like vertx.
It would be interesting to have a way of writing asynchronous methods, either with the Jax-RS 2.0 AsyncResponse (which is quite complex) or by letting the methods have a way of calling a "resume" method with the result as a parameter.
The text was updated successfully, but these errors were encountered: