(no title)
gr2m | 11 years ago
I'd be also very interested in your basic use cases that you think Hoodie couldn't handle. It would certainly be great input for the project.
gr2m | 11 years ago
I'd be also very interested in your basic use cases that you think Hoodie couldn't handle. It would certainly be great input for the project.
mcguire|11 years ago
You do realize that by putting it in your documentation, you're encouraging people to use it.
janl|11 years ago
What @gr2m means: there is no reason Hoodie’s mail feature would work any different from a traditional web app. At some point a server side will validate a client request, and if valid, translate that into sending an email (Gmail comes to mind). Hoodie’s email plugin can do exactly that, except that today’s implementation is a mere sketch of that, like other parts of Hoodie, that show what can be done, but aren’t hardened against production use, yet. None of that means though that Hoodie behaves any differently from a security/abuse/DOS perspective than any other web app :)
HackinOut|11 years ago
gr2m|11 years ago
I know this is nightmare to system architects / backend developers at first sight, but trust us, we know exactly what we are doing. We have excellent architects on our team, you just might not be our primary target group here.
But thanks for your feedback, much appreciated!