Hi, Yes, it is definitely a goal to have microsling and Sling upgrade compatible in way, that microsling applications (which are typically stored in JCR only) run unmodified on Sling. That is you can start developing in microsling and if you decide later, that this does not help solve you all problems, you can simple replace the microsling web app by the Sling web app in the servlet container and continue using the same repository and thus the old application.
Regards Felix Am Donnerstag, den 22.11.2007, 10:02 +0100 schrieb Alexander Klimetschek: > Hi all, > > from a sling user point of view (that I'd like to become as soon as > possible ;-) the separation into sling and microsling might be > confusing: Which one should I start with? Will it handle all my needs? > Can I start with microsling and upgrade to sling later? Maybe I start > with microsling, find it appealing but then wonder if an upgrade to > sling will keep the same level of happiness in the developer's mind. > Typically you will start with a simple example application where you > want to have good results in a short time. But if your project grows > or if you want to start a bigger application, you probably want all > the features that help structuring large applications (ie. the OSGI in > sling). > > My intuition says, it would be better to have only one framework that > gradually gets larger the more I need. So having a microsling feeling > at the beginning and all the other sling features later, maybe by > activating/adding bundles doing that. A successful popular example > like Ruby on Rails is simple to start with but has a lot of engines > helping you to do more as well as those helpful scaffolding scripts > (not that I want to compare RoR and sling! ;-). > > WDYT? > > Alex > > Am 22.11.2007 um 09:35 schrieb David Nuescheler: > > >> I think microsling is an excellent educational tool, which easily > >> shows > >> how Sling is supposed to work. In addition, microsling is also an > >> excellent prototyping tool to build very simple web applications > >> (wow, > >> what ist that again ?) without any super-duper needs. > >> If you need versatility, extensibility, special needs, .... (you > >> name it), you should turn to Sling. > > i think i agree: > > > > i think microsling is ideal for the rapid and agile "building" of an > > application > > sling is perfect for the enterprise heavy duty "running" of the > > application > > > > microsling is only on the left and sling is on the left and the > > right ;) > > > > regards, > > david > > -- > Alexander Klimetschek > [EMAIL PROTECTED] > > > >
