Notable highlights:
+ Beepbeep is now fully ported to support ewgi. Info and links at
http://beepbeep.dmitriid.com/documentation/middleware/
+ Beepbeep is now a fully ewgi-compatible midleware component itself
+ Implemented a Django-like middleware stack, see the link above
So, Beepbeep is now probably the first publicly available web-
framework to fully support the latest version of ewgi :)
Filippo and Hunter, thank you for your work and support. Honestly, I
was kind of sceptical of ewgi at first, but now I see it was the right
choice.
I've urged people to start porting Django and Rails middleware to ewgi.
I will also ask in mochiweb and yaws lists for their support for ewgi.
At the very least it would be nice to see a "ewgi.file_wrapper" for
fast serving of static files (similar to http://www.python.org/dev/peps/pep-0333/#optional-platform-specific-file-handling)
Future looks bright :)
Excellent, that's very impressive! Thanks for going out on a limb and
being the first.
> I will also ask in mochiweb and yaws lists for their support for ewgi.
> At the very least it would be nice to see a "ewgi.file_wrapper" for
> fast serving of static files (similar to http://www.python.org/dev/peps/pep-0333/#optional-platform-specific-file-handling)
This is also very promising. I've begun to try to create a set of
patches for the latest mochiweb and yaws which will offer "native"
ewgi support without requiring the ewgi reference implementation
project itself. Perhaps those patches will be an easy way to get
support accepted.
With regard to fast static file serving, yaws has a "sendfile"
linked-in driver which allows for static files to be served very
quickly. I agree that the ewgi standard should say something about
this. Does it make sense to simple allow an additional type in the
ewgi response tuple (element 4) of the form: {'ewgi.file_wrapper',
Filename}?
Best,
Hunter
Great news! Hope other frameworks will follow :-)
To me it makes a lot of sense :-).
cheers,
filippo
I will also ask in mochiweb and yaws lists for their support for ewgi.At the very least it would be nice to see a "ewgi.file_wrapper" forfast serving of static files (similar to http://www.python.org/dev/peps/pep-0333/#optional-platform-specific-file-handling)
This is also very promising. I've begun to try to create a set of
patches for the latest mochiweb and yaws which will offer "native"
ewgi support without requiring the ewgi reference implementation
project itself. Perhaps those patches will be an easy way to get
support accepted.
With regard to fast static file serving, yaws has a "sendfile"
linked-in driver which allows for static files to be served very
quickly. I agree that the ewgi standard should say something about
this. Does it make sense to simple allow an additional type in the
ewgi response tuple (element 4) of the form: {'ewgi.file_wrapper',
Filename}?
Ok, he answer on the mochiweb list was as follows:
[begin quote]
> Are there any plans to make Mochiweb ewgi-compatible?
> ewgi's author plans to take a shot at creating a patch for Yaws and
Mochiweb
> to make them natively compatible with ewgi. What's the community's
stance on
> this?
It's not something that we would be likely to implement on our own,
but it could happen if there's a patch that looks good.
[end quote]
Yaws list is silent
Ok, I will focus my efforts on the MochiWeb patch(es). Beepbeep
originally only worked with MochiWeb, correct?
Best,
Hunter
Indeed :)