[jboss-jira] [JBoss JIRA] (ELY-428) HTTP Mechanism configuration during deployment

[Pedro Igor (JIRA)]

    [ https://issues.jboss.org/browse/ELY-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179128#comment-13179128 ] 

Pedro Igor commented on ELY-428:
--------------------------------

Yes, that was the outcome from our HTTP discussions.

However, I was wondering if we didn't consider use cases where the initialization can take some time, thus blocking the first request. You never know what people can do, so that can have some impact on the application as well in the server.

> HTTP Mechanism configuration during deployment
> ----------------------------------------------
>
>                 Key: ELY-428
>                 URL: https://issues.jboss.org/browse/ELY-428
>             Project: WildFly Elytron
>          Issue Type: Enhancement
>          Components: HTTP
>    Affects Versions: 1.0.2.Final
>            Reporter: Pedro Igor
>            Assignee: Darran Lofthouse
>            Priority: Critical
>             Fix For: 1.1.0.Beta5
>
>
> It should be possible to configure a HTTP mechanism during deployment in order to parse/load configuration and reuse it in subsequent requests to an application.
> The most common use case for that is around mechanisms that need to read some configuration from inside a deployment (or provided by the mech config) when it is being deployed to the server.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)