Route function ( Handler < RoutingContext > arg0 , boolean arg1 ) { delegate . blockingHandler ( new Handler < io . vertx . ext . web . RoutingContext > ( ) { public void handle ( io . vertx . ext . web . RoutingContext arg2 ) { arg0 . handle ( RoutingContext . newInstance ( arg2 ) ) ; } } , arg1 ) ; return this ; }
specify a blocking request handler for the route . this method works just like io.vertx.rxjava.ext.web.route #handler excepted that it will run the blocking handler on a worker threadso that it wo n't block the event loop . note that it 's safe to call context.next from the blocking handler as it will be executed on the event loop context and not on the worker thread . if the blocking handler is ordered it means that any blocking handlers for the same context are never executed concurrently but always in the order they were called . the default value of ordered is true . if you do not want this behaviour and do n't mind if your blocking handlers are executed in parallel you can set ordered to false . concode_field_sep io.vertx.ext.web.Route delegate concode_field_sep Route failureHandler concode_elem_sep Route handler concode_elem_sep Route pathRegex concode_elem_sep Route method concode_elem_sep Route last concode_elem_sep Route useNormalisedPath concode_elem_sep Route newInstance concode_elem_sep Object getDelegate concode_elem_sep Route remove concode_elem_sep Route path concode_elem_sep Route disable concode_elem_sep Route enable concode_elem_sep Route produces concode_elem_sep String getPath concode_elem_sep Route consumes concode_elem_sep Route order