Jerome Dochez wrote:
>> Can something be done so that when the *first request* for
>> any app (or its component) that's deployed is sent,
>> the app initialization completes and the response is blocked
>> till that happens?
>>
>> That way, server can return as soon as possible and
>> first request to any app loads the app fully.
>>
>> Something similar was done in V2, IIRC.
> oh yes and we have seen how well that worked ;-)
>
> in general, it's very difficult to "predicts" all entry points of an
> application, some may be just a context root, some others may be web +
> ejb + web services + jms, well you name it...
>
> so this concept of blocking just does not work.
Is it too complicated to do this at a lower level? So, for instance,
the list of applications is initialized in an "incomplete" state.
When startup is done, it's marked "complete". Requests for the list
block until the state is "complete".