Touched, not typed. Erroneous words are a feature, not a typo. On Sep 3, 2014 5:56 PM, "Samith Dassanayake" <[email protected]> wrote: > > Hi, I have started working on the $subject[1] and it will be done in two phases > > Phase 1: Improve the usability > In current implementation there are around 7 usability issues. Most of these issues are caused due to, there is no proper indication of what is happening when a user add or update a custom subdomain. For example when a user adds a new custom subdomain and if it is failed, the error message does not specify whether issue is caused due to the unavailability of the subdomain or due to an internal server error etc... This is because currently we are not checking whether requested URL is available or not, before adding it. Therefore we will improve the behavior to reflect the status(whether the mapping is in progress, successful or unsuccessful) by checking existence of the requested custom URL before adding or updating in thread safe manner.
When a client call AddDomain REST API, it send a response with back end error message in case API call fail for some reason. Is it possible to display this error message so user get a better knowledge of what went wrong. Since there is no Update method for domain mapping from Stratos front, we will remove and add when there is an update request, until update method is available from Stratos side. This should be added to Stratos. Could you please create a jira in Stratos so update method will be implemented in next release. > > As an another improvement when one version is in production, we will make it to be the one with the production URL. This will happen based on two scenarios. > 1. When promoting from Testing stage to Production, if there is no version in production and production URL is specified, promoted version will be mapped to the production URL based on the permissions granted to the user. > 2. When adding(or updating) a production URL, if there is a single version(deployed) in Production stage, that version will be mapped to the production URL. > > Currently If custom URL is not mapped to any version, when we go to the URL it will respond with the status 404 since it is not mapped yet. We will improve this behavior such that If the production URL is not mapped to a version, we will map the URL to a page from WSO2 explaining that the URL will go live once it is moved to production and with the further instructions. > > > Phase 2 : Support for complete custom URL > In current implementation users can only specify the subdomain of the custom URL, which will be mapped under the domain wso2apps.com. In the 2nd phase we will allow users to add complete custom URL by having domain owner verification before setting up the custom domain. On app creation, we will assign a production URL by default, in the format of appid.tenantdomain.wso2apps.com and users can change the URL as they want, based on the permissions and validity of the domain. I will update more on this when this phase is started. > > [1] https://redmine.wso2.com/issues/3187 > > Thanks, > Samith > > -- > Best Regards > > Samith Dassanayake > Software Engineer, WSO2 Inc. > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
