Ian Bicking: the old part of his blog

What is WSGIKit?

Note: WSGIKit has been renamed to Python Paste

I think there's some confusion about what WSGIKit is, and what I intend for it to provide:

So... that's what WSGIKit is. I'd really like to support more frameworks, more servers, and bring more developers in. There's room! I'm willing to give commit access to anyone who's been around in the community, or really anyone who shows a little interest and competence (and of course plays well with others) -- the nice thing about version control is that nothing is permanent, so we might as well take advantage of that. I think WSGIKit has the potential to provide a compelling and simple installation and configuration experience for a whole variety of frameworks, removing the diversity that's not interesting but just annoying. At the same time it shouldn't infringe on any of the interesting diversity. It's also a good, testable, decoupled architecture to make a solid foundation.

Update: A couple people complained that I haven't actually said what WSGIKit is, maybe just where I think it should fit in. So...

So... what is WSGIKit? Maybe I'm a little confused now as well. I guess it's really about glue and reusable components to be provided to framework authors. Which puts it in a slightly funny place, because as glue it's actually front-facing to users in many ways. It's not an app server -- it can be run in a threaded, multiprocess, or CGI environment, embedded in Twisted, Apache, or another container. It's not a framework, those get built on top. It's not a template at all, nor any sort of model. It's just a lot of glue, I guess.

Created 15 Apr '05
Modified 23 Apr '05


Bah! This does not explain what WSGIKit is. It explains various things that it contains, but not what it's for. There I was thinking "ahahaha! now I will suddenly get to see what the whole WSGI thing is all about, since I am clearly not in touch with the Zen because I don't get it", and...this has not made things a lot clearer :-)

# sil

Sir Ian, Your Kung Foo is the greatest. But You still have not explained what WSGIKit is. Is it an app server? Where does it fit in the stack of Web server, templating engine, model and interface to the model?
# Count0

A picture might be worth a thousand words here...
# Ian Sparks

I think Mr. Sparks has it right here -- one rough graphic with some boxes and arrows could probably largely explain what you've clearly put a lot of time into writing. Perhaps a couple possible setups with well-known (in python webapp world at least) frameworks and/or behind apache with the parts labeled would probably explain it once and for all for the dim-witted or short of attention of us out here.

And if you happen to be on a Mac and/or have access to OmniGraffle that app makes almost any diagram look all fancy and special.

Also I keep sort of sensing the word 'substrate' as kind of what/where wsgikit is - maybe 'webstrate'. Assuming I kind of understand correctly...

# ToddG

Framework glue, huh? Pehaps you could call it "sticky" or "elmers", "Pyste" (python-paste or phonetically "pissed"). I'm envisioning frameworks as popsicle sticks or toothpicks and WSGIKit as the paste that holds it all together. Hmm... WSGIKit -> stikwig, swiktig, wisk, gitwisk, wig skit! Hmm... running "wsgi glue" through an gives "wiggles u". ;-) Hmm... What about "Waypoint"?
# Chad Walstrom

Just call it Chicago... as in "all roads lead to Chicago". ;-) Isn't that what WSGI is all about? For a more Euroasian reference, you could use "Constantinople", but that's pretty long. Besides, aren't you from the windy-city?
# Chad Walstrom

I'll add my voice to the general clamor of those who were hoping for an actual answer to the title question. I'm pretty sure now that it has more to do with web presentation than it does with scientific computing... but I was hoping to pin it down a bit more clearly. An example or two might help: "I would use WSGIKit when coding XXX because it provides YYY."

# Michael Chermside