One more thing that might not have been totally clear... Mojolicious is completely event loop based, and we are always watching if sockets become readable, even when we are still writing. So if you have a Mojolicious client and server on both sides, this whole topic becomes kinda meh, since you can bail out of parsing a huge request at any time by setting a parser error like i've done above. There would be no need to use 100 Continue, which is only useful for clients that can't read and write at the same time.
-- sebastian -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
