I'm the original author and project manager for Webware. I have read
your comparison to Webware at http://skunkweb.sourceforge.net/FAQ.html.
I'm writing to kindly ask you to remove this item from your list:
* Web Components. SkunkWeb encourages the componentization of your
web pages through caching and the like. It can also call components on
other SkunkWeb servers if you set it up to do so.
Webware promotes compententization through several means and was
designed to do so from the very start.
- Webware breaks down into discrete, focused packages.
- The app server is based on servlet factories, of which, you
can install your own.
- Servlets can internally forward messages to each other.
- Servlets can include each other's output.
- The app server supports XML-RPC and Pickle-RPC which facilitate
Pythonic communication between multiple app server instances.
As you can see, there is plenty of focus on components/objects in
Regarding caching, the app server caches all the servlets which in turn
decide for themselves what to cache. For example, a method might do
if self._foo is None:
self._foo = lotsOfWorkToComputeFoo()
So foo() only works hard the first time and on subsequent calls returns
the cached instance/string/whatever.
The app server doesn't directly get involved in your caching decisions,
as the semantics of your application really determine what can be
cached and for how long.
Also, MiddleKit caches objects extracted from databases and guarantees
their uniqueness (e.g., one distinct record never creates more than one
Python object in a given process).
There are probably several other interesting differences between our
products, but since I'm not familar with SkunkWeb, I can only correct
the misperceptions of Webware.
In any case, the implication that Webware is focused on components is
the item I really wanted to address the most. Probably the "caching"
comment should be removed as well.