Skip to content
This repository has been archived by the owner on Dec 26, 2022. It is now read-only.

Integrate proxy APIs to IOTA service #582

Open
YingHan-Chen opened this issue Apr 22, 2020 · 1 comment
Open

Integrate proxy APIs to IOTA service #582

YingHan-Chen opened this issue Apr 22, 2020 · 1 comment
Labels
A-api Area - Add/Revoke/Refactor APIs exposed by TA C-refactor Category - Improvement

Comments

@YingHan-Chen
Copy link
Contributor

Currently, we have two proxy modes.
One is proxy_passthrough that "Pass proxy API directly to IRI without processing"

In another mode, TA will deserialize the request then serialize again, pass the request to IRI, deserialize the result then serialize again. I think deserialize-serialize then serialize-deserialize is meanless.

Also, without passthrough mode, we get errors when the serialize/deserialize the request/result to the Hornet. In passthrough mode, the proxy works fine.

@howjmay
Copy link
Contributor

howjmay commented Apr 23, 2020

There are some core APIs not supported in the multiple serializing mode, and we do the serialization is actually for future optimization. We may apply caching or dcurl for the mode that we do serialization for several times.

However, setting proxy_passthrough as default mode may be a good idea.

@howjmay howjmay added A-api Area - Add/Revoke/Refactor APIs exposed by TA C-refactor Category - Improvement labels Apr 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-api Area - Add/Revoke/Refactor APIs exposed by TA C-refactor Category - Improvement
Projects
None yet
Development

No branches or pull requests

2 participants