Divyansh200102 commented on issue #5425: URL: https://github.com/apache/shenyu/issues/5425#issuecomment-2015200603
> > 1. While WASM doesn't natively support threads, how will the KitexPlugin leverage alternative WASM concurrency mechanisms (e.g., WebAssembly SIMD instructions, asynchronous tasks) to handle Kitex's asynchronous service calls efficiently within the WASM environment? > > 2. Are there any limitations or specific considerations for handling asynchronous operations within the WASM context for Kitex service calls? This could involve potential deadlocks, race conditions, or limitations on the number of concurrent operations supported by the chosen WASM concurrency approach. > > The Java part of KitexPlugin uses multithreading, while the WASM part uses single threading. > > > 3. Can the KitexPlugin leverage WASM exception handling mechanisms (if available) to capture and report WASM-specific errors that might occur during Kitex service calls within the WASM module? This could provide more granular error information compared to standard Go errors for debugging purposes. > > At present, WasmPlugin has not considered the error handle part, your suggestion is a good idea. While WASM doesn't have standardized exception handling yet, are there any experimental proposals or libraries we can explore to capture and report WASM-specific errors during Kitex calls? Also considering the potential overhead of loading and initializing WASM modules, will the KitexPlugin implement any caching mechanisms for frequently used Kitex service WASM modules? -- 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]
