AW: [Openinteract-help] Where to start?

[Andreas.Nolte@Bertelsmann.de]

Hi Tim,

a few months ago I sketched some ideas I had on OI application design =
to
this group, which you might be able to find in the mailinglist archive.

The main points are really, that you should separate your application =
logic
from the OI handler code as much as makes sense. If you use the =
Template
Toolkit, you can stuff your business objects into the template and use =
the
functions there, as you would do from batch jobs. This means, that you
should not put much logic into the templates either, but rather use =
custom
objects which you can stuff into these templates.

What we also often use is SPOPS with additional business functionality
pulled into the objects. But this also works from batch jobs - it does =
not
have much to do with OI really - OI only uses SPOPS.=20

Speaking of OI and SPOPS: you should use the build in Security =
sparingly,
because there is a chance, that you really slow down your system. The
approach that we are using is, that we map groups to handler security =
to
allow a group of users to access an application. But the security on =
the
acual data is handled by the application - not SPOPS.

I hope this helps a little...

cheers
Andreas Nolte=20
Leitung IT
-------------------------------------------------
arvato direct services
Olympiastra=DFe 1
26419 Schortens
Germany
http://www.arvato.com/
and...@be...
Telefon +49 (0) 44 21 - 76-84002
Telefax +49 (0) 44 21 - 76-84111



-----Urspr=FCngliche Nachricht-----
Von: Timothy M. Adamec [mailto:ti...@ad...]=20
Gesendet: Mittwoch, 26. Mai 2004 07:26
An: ope...@li...
Betreff: [Openinteract-help] Where to start?


Hello,

I've recently discovered and installed OpenInteract for a project I'm
working on and I'm overwhelmed with what it can do. I've never used an
application framework before, so I'm a little overwhelmed with what OI
offers.

Typical applications I've developed in the past have gone something =
like
this:

 * Design the database
 * Figure out what kinds of business rules are needed.
 * Code the business rules layer.
 * Design the front end using the implemented business rules.
 * Figure out what kinds of "behind the scenes" processing is needed.
 * Code the batch processing jobs.
 * Lather, rinse, repeat.

While searching through the OI docs, I didn't see much on the design =
theory.
For example, I've got a web-based sales application I need to write and =
it
some heavy logic requirements for commissions. Typically, I'd implement =
the
business rules as a set of pluggable classes to a generic commission =
module
and then batch process them at night. Is this something that OI is well
suited to?

I'm beginning to think that I need to look into coding most of those
"off-line" business rules and objects using the SPOPS framework and =
then tie
any needed functionality into an OI application. Am I on the right =
track?
And does anybody have examples on how to do this?

Thanks a bunch!

/tma



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle =
10g.=20
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3D3149&alloc_id=3D8166&op=3Dclick
_______________________________________________
openinteract-help mailing list ope...@li...
https://lists.sourceforge.net/lists/listinfo/openinteract-help