deceze

My guess: it's the call to `Zappa._clear_policy` as part of `unschedule_events` which removes all existing permission statements uncritically. I'm not sure if that conflicts with anything Zappa sets up itself,...

FWIW, my discovered facts and solution: - Our app uses a separate WebSocket API Gateway in addition to the default API Gateway that Zappa deploys. This is being set up...

API Gateway Websocket integration should be pretty straight forward: - API Gateway handles the persistency, so the Lambda handler/Zappa can remain stateless - API Gateway triggers events, which can invoke...

Sorry, I haven't touched this code or ejabberd since 2011 and am really not in a position to fix this. I'd happily accept a PR if you find the issue...

You can't really make a part optional at this point, you'd have to define two separate routes for this: ``` $r->add('/\w{2}:lang/pages/:title', ...); $r->add('/pages/:title', ...); ``` If you have to do...

This project may be considered abandoned. There's a more official HTTP domain available now as part of the official Sphinx extensions: http://packages.python.org/sphinxcontrib-httpdomain/

Sorry, not really. Maybe someday in the future, but currently I have no interest or time. I'd recommend you take this up with the maintainer of the official HTTP domain...

That functionality is already available through the regular dispatcher array: ``` php $r->add('/', ['homepage']); $r->add('/news/\d+:id', ['news']); $r->reverseRoute(['homepage']); $r->reverseRoute(['news', 'id' => 42]); ``` Not sure it's worth complicating the API just...

I have tentatively pulled your changes into a separate branch to test them in some real world scenario. I have scaled the changes back a bit, I don't think the...

Yeah, I understand why you did it, but that's a pretty inelegant solution. With this you need to repeat irrelevant parameters when calling reverse route methods, which kind of makes...