Next | Query returned 17 messages, browsing 11 to 20 | previous

History of commit frequency

CVS Commit History:


   2004-02-26 23:52:11 by Michal Pasternak | Files touched by this commit (1)
Log message:
Add PYBINMODULE

   2004-02-26 23:49:55 by Michal Pasternak | Files touched by this commit (2)
Log message:
zip -> tgz, as pointed by Min Sik Kim

   2004-02-26 22:14:27 by Michal Pasternak | Files touched by this commit (1)
Log message:
Dont -L in EXTRACT_OPTS.zip

   2004-02-26 22:02:28 by Michal Pasternak | Files touched by this commit (1)
Log message:
Add bl3

   2004-02-26 21:55:02 by Michal Pasternak | Files touched by this commit (1)
Log message:
Old DESCR was a misunderstanding, my fault

   2004-02-26 21:40:22 by Michal Pasternak | Files touched by this commit (1)
Log message:
Forgot about | brain after print-PLIST

   2004-02-26 21:37:43 by Michal Pasternak | Files touched by this commit (4) | Imported package
Log message:
PEAK is the "Python Enterprise Application Kit". If you develop \ 
"enterprise"
applications with Python, or indeed almost any sort of application with
Python, PEAK may help you do it faster, easier, on a larger scale, and with
fewer defects than ever before. The key is component-based development, on a
reliable infrastructure.

PEAK is an application kit, and applications are made from components. PEAK
provides you with a component architecture, component infrastructure, and
various general-purpose components and component frameworks for building
applications. As with J2EE, the idea is to let you stop reinventing
architectural and infrastructure wheels, so you can put more time into your
actual application.

But PEAK is different from J2EE: it's a single, free implementation of
simpler API's based on an easier-to-use language that can nonetheless scale
with better performance than J2EE.

Next | Query returned 17 messages, browsing 11 to 20 | previous