Yukang

Anyway, the current implementation could process an image smaller than 65535(HTTP request body length). we can fix the issues in the future. https://github.com/second-state/dapr-wasm/pull/19

> We would like to create two sidecars that are just `wasmedge` or `wasmedge-tensorflow-lite`. Instead of using GO or Rust to implement HTTP servers and then bootstrap wasmedge, we would...

> Can you update the architecture diagram in README to reflect the new microservice? will do it.

> when i run the image-api-go upload hotdog.jpeg,but return == APP == [xxx] [error] jpeg is invalid. Thanks for reporting issue. Could you please upload the invliad jpeg file here....

> Very glad and looking forward to seeing it! > > I am also interested in combining dapr with wasm, and am now a newbie to wasm. I am more...

Hi @tpmccallum , thanks for reporting this issue. [components](https://docs.dapr.io/concepts/components-concept/) is a core concept of Dapr, but we haven't used for this demo-application, such as `pubsub`, `schedule`, etc. So, we'd better...

FYI: https://github.com/second-state/dapr-wasm/issues/17 Dapr will try to check API when starting up: 

> Could the Dapr check sends a "proper" http request with a header? The telnet request is technically not http. I know the reason now. We must run the command...

I don't know the root cause, why do we have this limitation？ ```console wasmedge --dir .:. ../target/wasm32-wasi/release/wasmedge_quickjs.wasm http_server_demo.js ``` can not start the server properly.

> Just to make sure -- if you do not use `nohup`, you will need to start the server in one terminal and run the HTTP client in another terminal...