Ok, fair enough. Thanks for these thoughts. Cheers, =David
> On Oct 10, 2018, at 16:11, Tim Ward <tim.w...@paremus.com> wrote: > > It also provides a way to have separate user sessions (useful), different > security configurations (useful), management of static resource mappings > (useful), isolation of redirection to named servlets (less useful) and I’m > sure a bunch of other things. > > Tim > > Sent from my iPhone > >> On 9 Oct 2018, at 22:48, David Leangen via osgi-dev <osgi-dev@mail.osgi.org> >> wrote: >> >> >> Hi! >> >> From what I understand, ServletContext is not really thought about much in a >> non-OSGi application because there is basically one ServletContext per app. >> I never really gave it much thought before. >> >> In OSGi, we have more flexibility. >> >> So my question: when should I consider using a ServletContext other than the >> default context? I suspect that it could be useful as a cognitive division, >> but that’s about the only use I can see. And the advantage is not that great >> because users don’t see any difference at all, as far as I can tell. >> >> >> Any thoughts? >> >> >> Cheers, >> =David >> >> >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org >> https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
