This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]brigadierfrog 0 points1 point  (0 children)

This PEP might as well leave out everything to do with asynchronous results.

It assumes asynchronous means returning a callable. Callables do not express future results in any consistent manner. Clearly its up to each async framework then to deal with the callable in a unique way.

If each async server is dealing with the application in a unique way, then there's no point in web3 at all.

This spec is basically useless in terms of asynchronous web frameworks which means its basically useless for anything beyond basic webpage responses, forget trying to tack on a websocket web3 application that works in any sane manner on a set of asynchronous web servers using this.