> > Bringing the whole thing will be an expensive operation in the fist time > before caching them, IMO we should load page wise and then cache them. WDYT > ? > Bringing it one time is always faster, and much simpler to debug ect.
http://stackoverflow.com/questions/9855545/http-requests-vs-file-size On Fri, Mar 24, 2017 at 5:14 PM, Kasun Thennakoon <kasu...@wso2.com> wrote: > Hi all, > > > On Fri, Mar 24, 2017 at 4:13 PM, Chanaka Jayasena <chan...@wso2.com> > wrote: > >> I think we can do the same we did with jaggery base APIM UI using i18next >> library. http://i18next.com/ >> > > +1 to use i18next[1], > We could use the *i18next-xhr-backend* with the support from UUF to > provide i18n msf4j service to get the language mapping data.It also support > cache via local storage. So IMHO embeding similar functionality into UUF > client would be like re inventing the wheel.If we going to use i18next > library, all we need is simple locale service, which other wise we need to > have service + client library too. > > [1]: http://i18next.com/ > [2]: http://i18next.com/docs/ecosystem/#caches > -- > *Kasun Thennakoon* > Software Engineer > WSO2, Inc. > Mobile:+94 711661919 > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
