JS: Allow the possibility for providing query options when using jolokia.register() #78
Comments
I should have read #61 more closely ;-). Providing individual options for register() doesnt work easily because all scheduled requests are sent together in a single bulk requests sharing the same options. A solution would be to allow options within the request object itself, overriding options given as query parameters (will work for POST only, though). The alternative to split the bulk requests for different options given in register() is not very useful because of the complexity and undetermined runtime behaviour (whether 1 or 2 or 3 ... HTTP requests are sent is not transparent). |
Since for bulk requests each single request should be able to have individual processing options. The best way to implenent this is to add a The JavaScript API must also be adapted to allow request based options when registering requests as jobs. |
Well, I'm getting old ;-) |
Currently it is not possible to provide processing options (transported via query options) when using
j4p.register(...)
in the JavaScript client. In this case, processing options can only be given to constructor of the Jolokia client. One could use individual client objects with different processing options, but this is an overhead which can be avoided when allowing processing options directly when registering jobs.See also #61 for a former discussion with the same issue.
The text was updated successfully, but these errors were encountered: