hello, i tend to use uWSGI for nearly everything, even very basic or one-time-use applications, simply because it solves many problems and offers features that said apps.
one problem i've had for awhile now is how to properly run apps that require no incoming --socket, or really, an uWSGI-managed event loop of any kind... recent examples: ) AMQP consumer/worker ) team-oriented IRC bot ) vpython realtime analyzer/demonstration ... is there any way to run such applications in a natural way? currently i run them as mules, and set `--processes=0` in addition to `--socket=@null` (or some variant). while this works well enough it's really more of a hack, and in this specific case i'd like to use the tracebacker but that doesn't seem to work on mules. i've also tried using `--command-mode` but that has nasty side effects like not processing touch-reloads, and `--worker-exec` means no services at all :( essentially i want uWSGI to neither care nor require an explicit loop, and expect workers to block on their own... and the end of the day i potentially want to use any of the services uWSGI has to offer (general-purpose application container) *EXCEPT* parsing/handling/delegating an "incoming stream"... seeking a "noop loop" if-you-will. ...thoughts? loop-engine/plugin required (if possible at all)? -- C Anthony _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
