-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add async support #6
Comments
How is progress going on this? Have you thought about how you might go about implementing it? I was thinking of taking a shot at it but don't want to if you've already done a significant amount of work on it. |
I haven't really written any code for this yet, feel free to have a go at it. I'm thinking that this and #7 is related, since both "require" you to parse the defensio response outside the |
Defensio does have the option of providing a callback URL so they can POST the results of a comment back to you. This probably wouldn't require the use of background workers, right? |
I'm sorry, I was thinking of an odd way of implementing this. Basically what you need is a way to tell the model, or Defender, "hey, I got this from Defensio, please do something with it!" |
EDIT: Forgot to say I'm working on this at the mo! From my point of view I'd rather it dealt with it as much as possible i.e. what I have at the moment is:
Obviously this is going to add a few extra requirements from Rails:
Are you okay with me adding these extra as dependencies or do you have a better way of doing this that doesn't tie it down so much? |
Just to give you an idea of where I'm going with this: |
Defensio supports asynchronous requests, and Defender should as well. This might shorten the load times on web sites.
The text was updated successfully, but these errors were encountered: