Hi Thushara,
In the existing logic, UI bundle will pass the URL to the backend and importResource method will fetch the content from the URL. With the proposed implementation, UI bundle will fetch the content and send it to the backend. In both implementations UI will wait until import operation completes in server side. Therefore I believe no client-side performance will associated with this change. Regards, Chandana On Sun, Jan 4, 2015 at 4:28 PM, Thushara Ranawaka <[email protected]> wrote: > Hi, > > In order to do the WSDL/WADL/Schema/Policy upload path change[1], we need > to download resource[2] content. Therefore I propose URLConnection[3] to do > this in java UI level[4]. Below is the sample code segment made to do this. > > URL sourceURL = new URL(fetchURL); > in = new BufferedReader( > new InputStreamReader(sourceURL.openConnection().getInputStream())); > > fetchURL will be the resource URL user input. > > Please share any ideas on this, such as client-side performance overheads > etc and security limitations. > > [1] - GReg - WSDL/WADL/Schema/Policy upload path change - mail thread > [2] - WSDL/WADL/Schema/Policy > [3] - > http://docs.oracle.com/javase/tutorial/networking/urls/readingWriting.html > [4] - org.wso2.carbon.registry.resource.ui/ImportResourceProcessor.process > > Thanks, > -- > Thushara Kasun Ranawaka > Software Engineer > WSO2 Inc.; <http://www.wso2.com> > lean.enterprise.middleware > Mobile : *+94 (0) 773438949 <%2B94%20%280%29%20773438949>* > *[email protected] <[email protected]>* > -- *Chandana Napagoda* Senior Software Engineer WSO2 Inc. - http://wso2.org *Email : [email protected] <[email protected]>**Mobile : +94718169299* *Blog : http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
