The confidential port is not too important to me. I have been playing with  the PaaS Openshift [1]. which needs to listen on a IP address that is runtime determined

With  confidential port I am just doing a one-off change to say 15000 to get it in the openshift allowed range. I can do that as part of the platform setup.

/Andy

[1] https://openshift.redhat.com/app/
[2] https://openshift.redhat.com/community/kb/kb-e1038-i-cant-bind-to-a-port

On Thu, Nov 15, 2012 at 2:04 PM, Christian Grün <christian.gruen@gmail.com> wrote:
..added. There is no option yet for the confidential port, as it
required a number of additional options. Anyway, if you think that
would be useful, we could easily add such an option.
___________________________

> I am often getting caught out by the fact that in recent 7.5 builds the http
> properties are ignored unless they are set by editing jetty.xml.
> I wonder if the supplied jetty.xml  could use <SystemProperty>. Something
> like:
>
>   <New class="org.eclipse.jetty.server.nio.SelectChannelConnector">
>    <!-- host sometimes needed in PaaS envronment -->
>     <Set name="host"><SystemProperty name="org.basex.serverhost"
> default=""/></Set>
>         <Set name="port"><SystemProperty name="org.basex.serverport"
> default="8984"/></Set>
>         <Set name="confidentialPort"><SystemProperty name="org.basex.??"
> default="??"/></Set>
>         <Set name="maxIdleTime">60000</Set>
>         <Set name="reuseAddress">false</Set>
>         <Set name="Acceptors">2</Set>
>       </New>
> /Andy
>
>
> [1] http://docs.basex.org/wiki/Options
>
> _______________________________________________
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>