What response we should be able to handle?
(Main topic discussion Syscall and ApplicationEngine https://github.com/neo-project/neo/issues/1275)
I prefer JSON only.
Json only is good for me too
@shargon Could you please clarify what response do you mean here? Is that just about the format to store responses in ResultCache?
Do we want to build web crawlers on oracles? 馃槀
there are two approaches, consuming a standard service, perhaps json as @erikzhang mentioned,or global data dump,including html,and parse it to get information,not quite from an API,but from anything. I see benefits in both, but I prefer a global approach, as long as response type is identified (application/json for example, and user may reject others).
The reason is that we may integrate smart contracts to existing services, perhaps LDAP for authentication, or even OAuth2. It makes sense from a globalized internet perspective. As long as we have https, and safe dns (dns sec) we can do amazing things.
Could you please clarify what response do you mean here? Is that just about the format to store responses in ResultCache?
We have filters, but you need a filter for every format, the filter for XML is different than JSON. So first, we need to know which kind of responses we will allow.
But my question is more about. If we decided that the filter is OK for us (i hope so xD) we need to know wich filters we will implement. If your download return a raw text file, and you don't use a filter is good to me, expensive but good. Maybe the question is more about wich kind of filters we want?
We should recognize the format of the object based on its Content-Type. The user should clearly indicate what Content-Type he accepts. We can only support application/json first. In the future we can support more Content-Type.
I agree with JSON and I also agree that we should support additional responses in the future. I think that there will be occasions where the smart-contract developer won't have access to a JSON API.
Perfect, the first accepted response to be implemented is JSON and the Content-Type response should match this.
The current version doesn't care about the Accepted-Response I think that the filter should be used for parse the json, the xml or other formats.
馃憤 Thumb Up if you are agree, we should accept any response .
馃憥 Thumb Down if you think that we need accept only json.
@neo-project/core @neo-project/ngd-seattle @neo-project/ngd-shanghai @realloc @roman-khimov
I think that it will be easier and safer with a whitelist control https://github.com/neo-project/neo/pull/1591
Close? It's moved to neo-modules/OracleService.
Most helpful comment
The current version doesn't care about the
Accepted-ResponseI think that the filter should be used for parse the json, the xml or other formats.馃憤 Thumb Up if you are agree, we should accept any response .
馃憥 Thumb Down if you think that we need accept only
json.@neo-project/core @neo-project/ngd-seattle @neo-project/ngd-shanghai @realloc @roman-khimov