> Hi all,
> I'm developping a web application with several services. I'd like to
> build this application as a SOA (service oriented architecture)
> platform, so that it will be easy to update and/or add services.
> The way I'm about to write my application is to build TG applications
> like this:
> - base application (including global model, authentication, master
> template, etc)
> - app_1 including brain for a batch of services (lib, templates,
> - app_2 including brain for another batch of services (lib, templates,
> - ...
> Everything being linked with the base application.
> For example, the parts I'd like to add to the base application are:
> - reusable icons
> - helper functions
> - ORM and data model
> - base templates
> What would be the best way to do? Should I do something like tg
> extensions or tg applications? (I believe TG applications is the right
> way to do...)
> What method for development? Working with "virtual" eggs like if I add
> installed my applications? Is there any tutorial about this?
> Thanks for your help.
A related question is: how do you manage dependencies between
modules/applications? By setup parameters? Hard links? ...
Here comes an example: I want to manage two types of media, eg. video
and photo. I'd like to build a "video" application which will allow to
add/edit/delete/search/share videos. I'd also build an application for
similar tasks for images (but also including images from other websites,
for example). => 2 applications.
Both will allow to add comments, tags, etc. => another application?
Would you make something like "application inheritance"? What about a
"helper" comment application?