No need for csrf token in rest architecture. because we may have a other ui
approaches like reactjs library where we handle those stuff's. So it's
better to avoid csf. use csrf_exempt decorator.
this link may explain you what you need after adding csrf exempt decorator
https://stackoverflow.com/q
Hi Suryakumar,
Thank you very much for your reply.
I'm actually NOT using React.js in my front end.
I'm using Bootstrap, jQuery and ajax calls.
Do you reckon still better to avoid CSRF in my template views?
Thank you very much!
Regards,
Alex
On Tuesday, March 12, 2019 at 4:10:45 PM UTC+9, Su
Hi All,
I had the rest URL like(https://marketguru/django/mongodb). I call
that URL to POST a record into store various database like Mysql, MongoDB,
Mlab. For Post a record I am using only one common REST
URL(https://marketguru/django/mongodb). I call that URL from 4 salesforces
strea
Have you looked at celery and redis?
Mark
On Mon, Mar 11, 2019 at 10:32 PM mohamed fazil
wrote:
> I am using Django rest framework. I had a rest URL when i call that URL at
> a time from various 3, 4 streaming client, I got a response from only one
> client remaining client not responding me fo
Yes phillips both we looked but not useful to this problem. Thanks for your
kind reply. Any other suggestion is there please suggest me
Thanks
Fazil
Skits Private Ltd.
On Tue, Mar 12, 2019 at 8:38 PM Mark Phillips
wrote:
> Have you looked at celery and redis?
>
> Mark
>
> On Mon, Mar 11, 2019
And celery not working python 3.7 or above
Fazil
Skits Private Ltd.
On Wed, Mar 13, 2019 at 9:50 AM mohamed fazil
wrote:
> Yes phillips both we looked but not useful to this problem. Thanks for
> your kind reply. Any other suggestion is there please suggest me
>
> Thanks
> Fazil
> Skits Privat
Not sure if DRF is designed for multi-threading. I believe it’s just a
web-framework.
Specifics like multiple-threading etc. should be better offloaded to other
tools/frameworks like celery, pyspark, numpy, dask etc.
If required, plug these tools/frameworks inside serializers, views, signals
etc.
And for the streaming problem — cache serializers, responses at
web-server(nginx/apache) may help?
But I’m not sure it will last for long, because 3-4 concurrent clients are
too less to be having any problem in prod env and in-general number of
clients grow fast.
On 13 March 2019 at 11:12:46 AM,
