Croway commented on PR #25778: URL: https://github.com/apache/camel/pull/25778#issuecomment-5436653243
Hello @ramu11 thanks for working on this! I see you implemented option A, the simpler one, that is fine as a first step. But I do think that in the future we should look into expanding this component capabilities to be in parity with the javascript one, since it is a language (like javascript), at least my expectation, is that they behave similarly, and hopefully, javascript can be easily replaced with quicks gaining portability (and hopefully) performance. To sum up, right now, it is possible to `Read body/headers/properties`, what the javascript component offer other than the read is: * `Mutate headers/properties from JS` * `Call Java / Camel APIs` We can merge the PR as is, but it would be nice to check if implementing these features is feasible, and how javascript and quicks behave performance wise (a blogpost would comparing the two would be nice). @davsclaus @oscerd wdyt? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
