[05:30:46] [connected at Thu Jan 11 05:30:46 2007] [05:30:46] <> *** Looking up your hostname... [05:30:46] <> *** Checking ident [05:30:46] <> *** No identd (auth) response [05:30:46] <> *** Found your hostname [05:30:46] <> *** Your host is anthony.freenode.net[anthony.freenode.net/6667], running version hyperion-1.0.2b [05:30:48] [I have joined #peak] [05:54:15] ** Jenn5 has left IRC (Remote closed the connection) [11:03:11] ** bitmvnch has joined us [11:04:01] ** bitmvnch has left IRC (Client Quit) [11:04:09] ** bitmvnch has joined us [11:56:16] ** pje has joined us [12:26:26] pje is now known as pje_mtg [12:29:12] ** AniHatzis has joined us [12:30:14] hi @all [12:30:48] is peak still in development? the website states in download->current releases "may 2002" [12:30:53] sorry, may 2003 [12:30:54] ? [12:42:08] yes, it's still in development; will talk more when I'm out of this meeting [12:43:09] setutptools still have a fairly active release cycle, it think 0.6c5 was just pushed a few days ago [13:14:29] thank you. i'm also in meeting. brb [13:50:27] ** coderanger has left IRC () [13:51:59] bitmvnch is now known as recyclemvnch [14:02:48] ** recyclemvnch has left IRC () [14:40:44] pje_mtg is now known as pje [14:41:37] So, PEAK as an overall project is alive and well, although as coderanger said, the emphasis in the last year or two has been heavily on setuptools [14:43:07] But, most of the PEAK core APIs (binding, naming, config, etc.) are being mostly maintained, with little new development [14:43:30] I occasionally add new SQL drivers or features when I need them for projects, but that's about it. [14:44:09] I definitely fix bugs, though, and answer questions. So I guess you could say the project has stabilized in permanent instability. :) [15:30:08] :) [15:30:49] pje: i'm too sorry, the meeting still lasts but i have a short rest [15:31:05] not a problem [15:32:53] i'm looking for some kind of distributed business components where business logic is in a layer and objects only accessible through a specific API (remote where clients can be other business components, GUIs, web-apps...) [15:33:19] of course all in python :) [15:34:01] in short: a n-tier/multi-tier architecture for python apps [15:34:23] i learned of peak due to easy_install [15:35:02] at the first look on peak i got the feeling that peak is probably what i'm looking for [15:58:56] in some respects, yes. PEAK was designed to handle the app/storage layers. [15:59:38] And the assumption was that a web layer would be coupled via Python (in-process) to an app layer. [16:00:05] So, three tiers, but only 2 processes (i.e. Python and db server) [16:00:36] There's nothing in PEAK to support a client layer other than command-line tools, although there are some third-party packages (and private projects) that have used PEAK in GUI layers as well. [16:00:51] some of them using Twisted for remote access/messaging, too. [16:10:51] i have built a prototype of a back-end (local in-process API to business component + database layer) as flavor [16:11:51] for a model-driven software development tool chain in python [16:12:24] UI and remote clients at all are totally missing [16:14:02] but a local python module can connect to the component, retrieve an operation object (representing a database transaction) which is used in all calls on business objects, plus some methods to retrieve objects from the owning component or objects linked to them [16:14:30] i want to replace the target architecture prototype by something else [16:14:38] this is the reason why i look for one :) [16:14:56] BTW: the project is OpenSwarm, http://openswarm.sourceforge.net/ [16:20:21] ** bitmvnch has joined us [16:21:04] Interesting. PEAK doesn't do XMI 2.0, let alone 2.1. I ended up not focusing on MDA so much once I stopped working in an "enterprise" a few years ago. :) [16:22:26] openswarm doesn't use XMI for data exchange between components. it is only used by the SDK to import serialized UML models specifying the application which should be generated [16:24:26] so the SDK "understands" an UML model saved as XMI. i.e. it parses a "Class" element and knows what kind of business class and modules to produce in python, including attributes, getters/setters for attributes and associations, some SQL stuff for the ORM layer etc. [16:25:20] you surely will agree that building a target architecture for python enterprise apps is not easy :) [16:26:14] so the architecture i have is a nice prototype to show what openswarm is supposed to be, but i need something stable, robust, etc. [16:33:05] Right, I was just saying that PEAK only does XMI 1.0 through 1.2, and those read-only; it also has metamodels for XML 1.[3-5], and CWM 1.[01], and MOF 1.3.1 [16:33:40] (see the peak.metamodels package in the SVN version) [16:37:59] thanks for the hint. that's interesting. i wonder why you have these metamodels in peak... did you work on mda features? or do you use the metamodels just for runtime data [exchange]? [16:48:13] UML, code generator? you already started a MDA for PEAK? [16:50:49] i have to go for lunch, uhm, actually midnight lunch. [16:51:16] i will study more of PEAK and will come back to this channel [16:51:46] thank you [16:52:57] cu! [16:56:36] ** AniHatzis has left IRC ("unplugged") [18:44:25] ** bitmvnch has left IRC () [18:46:16] ** bitmvnch has joined us [20:47:09] ** bitmvnch has left IRC () [21:24:24] ** bitmvnch has joined us [21:25:51] ** bitmvnch has left IRC (Client Quit) [22:05:57] ** bitmvnch has joined us [22:13:42] ** bitmvnch has left IRC () [22:35:47] ** pje has left IRC ("Client exiting") [23:36:32] ** bitmvnch has joined us [23:47:14] ** bitmvnch has left IRC () [23:48:17] ** bitmvnch has joined us [23:49:20] ** bitmvnch has left IRC (Client Quit) [23:52:34] ** bitmvnch has joined us [23:57:41] ** bitmvnch has left IRC ()