I've just finished the wiki tutorial and now I'm trying to build an intranet
app. I've got 10+ years of Python experience but most of my web stuff to
date is simple cgi or JSP.
Objective: We've got a lot of legacy code that needs to invoke Python to do
some business rule stuff. The API is based on HTTP. Generally there is no
need to respond with a web page, just an "OK" or some simple json. There is
not a significant throughput requirement, 100~1000 hits a day is a good
guess.
But we have numerous small, unrelated or loosely coupled business rules.
I'm developing the business rules as standalone logic with it's own test
scripts, independent of any web related issues; then just placing the on
PYTHONPATH. All this will run on a single server.
What is recommended:
1. A different turbogears project for each "business app" which would
then
require a different port. Requires a little config management to keep track
of the ports, but separates them better, and allows independent restart.
2. Or a single project with a "subcontroller" for each business app.
Provides a single "master node" and everything under that. In a small
company (I'm the only Python programmer) this provides ease of tracking
what's "out there".
I realize this is probably subjective, but I would appreciate knowing what
others have encountered. Once I deploy my first app, it's pretty hard to
backtrack, given that the legacy code I'm supporting is out of my hands.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
