the installation for 'any other site' is broken... any clues?
Yeah every client have to run the software or you use a proxy. If you have a site with many spreads you don't need a running instance. But if you have a an unknown site you would have to run a little server permanently.
I want to return values from external REST APIs to the client. Is it really that hard with the new async/await syntax?
Are there plans for django 2.0 to support asynchronous processing like in http://aiohttp.readthedocs.io/en/stable/ ? Everybody suggests celery as an asynchrone task queue, but i dont see how to resolve a http request…
the installation for 'any other site' is broken... any clues?
Yeah every client have to run the software or you use a proxy. If you have a site with many spreads you don't need a running instance. But if you have a an unknown site you would have to run a little server permanently.
I want to return values from external REST APIs to the client. Is it really that hard with the new async/await syntax?
Are there plans for django 2.0 to support asynchronous processing like in http://aiohttp.readthedocs.io/en/stable/ ? Everybody suggests celery as an asynchrone task queue, but i dont see how to resolve a http request…