Am 13.09.2014 13:12, schrieb Daniel Faust:
> Hi Tobias,
>
> yes, as a general twisted resource. It would be just as convenient as a
> wsgi resource. But I understand why one would want to avoid this.
Technically, it would be trivial to add another path service to Crossbar
that serves a general Twisted Web resource. However, to make that
practically useful, the resource would probably then want to talk WAMP /
wire up to a WAMP component. And this is exactly what is discourage
because of the spaghetti this will lead to (below).
Crossbar is a WAMP router. In addition, it can also serve static Web
files (and simple Jinja templating based Web pages). It is _not_ a
general Web framework for dynamic Web applications. This is the old
world, and there are plenty of frameworks like Django, Flask etc
> Specially if the resource should also be able to talk directly (in
> memory) to other components, as this can easily end up in becoming
> spaghetti code if care is not taken.
Exactly. I'd consider that bad design.
Nevertheless I'd be interested in learning what you do in your Twisted
Web resource that you cannot migrate out to a regular WAMP component.
> > an email to
crossbario+...@googlegroups.com <javascript:>
> > <mailto:
crossbario+...@googlegroups.com <javascript:>>.
> <javascript:>
> > <mailto:
cross...@googlegroups.com <javascript:>>.
> <
https://groups.google.com/d/msgid/crossbario/9df119f2-7d65-42a7-85f0-70ddbe833699%40googlegroups.com?utm_medium=email&utm_source=footer
> <
https://groups.google.com/d/optout>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Crossbar" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
crossbario+...@googlegroups.com
> <mailto:
crossbario+...@googlegroups.com>.
>
https://groups.google.com/d/msgid/crossbario/68f90801-adfa-4810-97d6-e905f92a6838%40googlegroups.com
> <
https://groups.google.com/d/msgid/crossbario/68f90801-adfa-4810-97d6-e905f92a6838%40googlegroups.com?utm_medium=email&utm_source=footer>.