Hi folks,
Thanks all for the great work done so far. Have thoroughly enjoyed
working with TG.
Unsure if this is the forum for adding some more thoughts for 2.0...
but, wanted to indicate that it may be helpful to come up with a
layered approach to component requirement.
For example, consider the case of deployment of a TG-based app in an
embedded systems environment. This is a perfect example that demands a
multi-tiered framework. Not always, do we have the luxury of an
embedded database. With or without a database, data of various formats
would have to be assembled behind the scenes. In this case, it would
help to "setup" a leaner version of the framework, and provide "shims"
to access/convert disparate types of data. Right now, its a little bit
unclear if one could "seperate" out db-related comps from the main
source base, and yet get it to work in an embedded system that has no
database. Also, in many such systems, space (hd/flash/etc) could be of
a premium, driving the need for a more layered approach. A "ezsetup.py
-no_db" or "tg_admin quickstart -no_db" may be a good option to have.
Other needs for embedded systems could include:
. non-db-based authentication via sessions/cookies
. the ability to get built-in log rotations/movement triggered by
age/size etc.
. builds/setup via cross-compiles (I should admit, cross compiling
TG was
a breeze (minimal changes), as compared to the changes to
python /
setuptools needed to support that.
Just some thoughts (from a narrow embedded systems perspective :-)...
Also, it may be helpful, if there could be a cpl-page doc somewhere
that
could describe (graphically) the role of each of the proposed pieces
of
TG 2.0 - so some of us could understand the architecture/interactions
a
lot better.
Thanks again, for all your efforts.
Regards,
/venkat
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
