On Tue, Feb 1, 2011 at 6:47 PM, Paul Fremantle <p...@wso2.com> wrote:
> Can we get the keystore management tied into our existing keystore manager? > Other aspects would be great to manage through a new QPid specific UI. > > BTW I don't personally see these as hard requirements for v1. Definitely > required for the next post v1 release. > +1. I think the only thing we need for this release is the default persistence support. Otherwise all the messagboxes and messages vanish if the server restarts. thanks, Amila. > > Paul > > On 1 February 2011 12:59, Danushka Menikkumbura <danus...@wso2.com> wrote: > >> How would we expect users/admins to change this in production? >>> >> >> We can have an admin UI that takes care of managing the conf files. >> >> >>> Are there other configuration settings that users will need to change? >>> >> >> Yes. A couple of things. >> >> - Keystores >> - AMQP-level settings (frame size, maximum, queue depth, maximum message >> size, message count, etc) >> - Ports - The default is the IANA-assigned port number for AMQP >> (i.e.5672) >> >> Danushka >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > Office: +44 844 484 8143 > Cell: +44 798 447 4618 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > p...@wso2.com > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other confidential > information and is intended exclusively for the addressee/s. If you are not > the intended recipient/s, or believe that you may have received this > communication in error, please reply to the sender indicating that fact and > delete the copy you received and in addition, you should not print, copy, > retransmit, disseminate, or otherwise use the information contained in this > communication. Internet communications cannot be guaranteed to be timely, > secure, error or virus-free. The sender does not accept liability for any > errors or omissions. > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
