[PEAK] need hints on PEAK twisted support

[ueck at net-labs.de]

Hi Stephen,

> >     schema (abstract sql-schema with sapdb-driver (readonly))
> 
> I'm very interested in abstract sql-schema representation.

CWM would possibly the way to go .. but i didn't find any
tool to Edit the Schema-Info freely available so i went on
with a simpler approach. i haven't used it for ages right now.

> 
> >     bsddb (a try to make a bsddb-datamanager .. doesn't really work)
> 
> You might want to check out ATOP, Glyph's latest persistence
> engine.  ;)  He gave a good talk at PyCon DC about it, and had
> lots of lessons-learned about BSDDB as a back-end.  Non-trivial.
>

does it come with twisted ?


> >   - workspace (concept of a Workspace, is also used in my webdemo.
> >                a workspace is the "controller" in MVC and is
> >                implemented in my libraries as statemachine as
> >                event-consumer, that interacts with the businessobjects
> >                on behalf of the user's actions and controls the 
> >                user-interface. this packages is not yet complete )
> 
> It would be interesting to give it a Twisted Perspective
> Broker interface to make it a "sharable workspace" in a
> potentially more flexible way than a web app could do ... :)

The whole system is designed as 4-Tier app:
 - UserInterface (Web/wxWidgets)
 - Workspace
 - BusinessModel (peak.model, business-rules)
 - DataStorage (datamanagers)

the communication should happen as async messages between
the components, that are either local or remote (configurable)

e.g. a wxClient would have UserInterface and Workspace within
one process and talk to the BusinessModel with remote-messages
while a WebApp would only be the UserInterface that talks with
http-requests to the workspace that lives on the server-side
(session-based).

this is the theory .. it's still a far way to go.

> > 
> > nllworkflow (actively developed and ready for a4)
> > ------------
> >   a Workflow Package that currently include an UML-1.3 like
> >   StateMachine. Future versions should also contain a WFMC
> >   Engine to be able to start ActivityBased and StateBased Processes.
> 
> I'd like to see if we can collaborate on this.  My partner
> on our app has developed a WFMC-based workflow app, but I'm
> not sure how the state machine under it works.

about 2 years ago i also developed a WFMC-Engine-Prototype with Transwarp
(PEAK is it's successor) that used a fairly similar aproach for scheduling
the activities as peak.events does right now. 
it's in our cvs in /oldlibs/NetLabsLibs/src/NLL/Services/Workflow/.

peak uses similar concepts, so a "major refactoring" would get it 
back from my codebase ;-)

I'm interested in sharing efforts for this as my time allows.
i have not yet started planning to work on wfmc for now.


> Yes, thanks!
> 
> Cheers,
> Steve

you're welcome

Ulrich 




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/