Hi, I'm -0 on this proposal. If we have different offsets for different products, we will have to maintain a document to show the offsets we have given for each product.
When doing product integrations, setting offset is not the only configuration step. It is a simple operation and I think it's better to let the user to do that along with other configurations. Then the user will know what really happens with ports and how to configure URLs. In most of the production deployments, the WSO2 instances will be in separate servers/VMs and we rarely modify the offset. Most of the time, we define common security groups to open ports. So, if we don't change offsets by default, we will be having common ports for each server. So, I think it's better to have no offsets by default in WSO2 products. Thanks! Best Regards, On Wed, Nov 12, 2014 at 5:42 PM, Paul Fremantle <[email protected]> wrote: > Ack? > > Paul > > On 10 October 2014 09:27, Paul Fremantle <[email protected]> wrote: > >> I have a simple proposal, which is that we predefine a standard offset >> for each product. >> >> e.g. AS 0, ESB 1, AM 2, GovReg 3, BAM 4, IS 5, etc... >> >> These would be baked into the distros. This would make life a lot easier >> for customers doing more than one product. Also for say BAM integration, >> life would be much better. >> >> Paul >> >> -- >> Paul Fremantle >> CTO and Co-Founder, WSO2 >> OASIS WS-RX TC Co-chair, Apache Member >> >> UK: +44 207 096 0336 >> >> blog: http://pzf.fremantle.org >> twitter.com/pzfreo >> [email protected] >> >> 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. >> > > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, Apache Member > > UK: +44 207 096 0336 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > [email protected] > > 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. > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
