It is up to you, just ask yourself: If Red5 team updates to Tomcat 7 can we easily revert our custom solution to the official Red5 one? Is usage of Tomcat 7 production ready (In other words: Could we potentially release Tomcat 7 and you can make your commits to trunk)? I guess you want those changes in trunk. I would prefer it too cause I could test and help better if we can concentrate on a single branch.
Sebasitan 2012/10/22 Maxim Solodovnik <[email protected]> > Yes, > > I need it to implement server push for Calendar and Chat. > > > On Mon, Oct 22, 2012 at 2:35 PM, [email protected] < > [email protected]> wrote: > >> Do you need those changes to continue your work? >> >> Sebastian >> >> >> 2012/10/22 Maxim Solodovnik <[email protected]> >> >>> Hello Sebastian, >>> >>> Finally I was able to patch Red5 so it can work under Tomcat 7. >>> Should I create custom patch in our sources? Or we are going to wait >>> until Paul will merge it into Red5 sources? >>> >>> >>> >>> >>> On Sun, Oct 14, 2012 at 7:12 PM, Maxim Solodovnik >>> <[email protected]>wrote: >>> >>>> AFAIK language files can be XML for wicket. So the number of files >>>> remains the same. Only format will slightly changed >>>> On Oct 14, 2012 6:31 PM, "[email protected]" <[email protected]> >>>> wrote: >>>> >>>>> I don't think that we can just remove features. >>>>> I general it is quite difficult to remove features in an Open Source >>>>> project, cause as soon as you start a discussion about it on the mailing >>>>> list there will be always somebody that tells you he needs that feature. >>>>> >>>>> The current language editing also has its advandtages. For example: >>>>> You have all labels in a single XML file (so its easier to translate), you >>>>> can export and import those at runtime, you can modify wording at runtime. >>>>> Having the labels spread in many .property files does require to >>>>> recompile the complete app for every label changed. And to translate the >>>>> files you would need some extra tools to have those labels editable also >>>>> for Non-Java programers. Property files are not UTF8 save. That means a >>>>> Russian property file contains nothing human readable but only something >>>>> like: >>>>> >>>>> \u00EF\u00BF\u00BD >>>>> >>>>> So, I am not a real fan of the i18n possibilities with .property >>>>> files. Having them in XML has a lot of advantages and importing them into >>>>> the DB makes it possible to edit them at runtime. >>>>> >>>>> Sebastian >>>>> >>>>> 2012/10/14 Maxim Solodovnik <[email protected]> >>>>> >>>>>> I ain't implemented backup/restore. I thought users will use command >>>>>> line instead. >>>>>> I also thought we can get rid of language editor in favor of wicket >>>>>> language files :) >>>>>> On Oct 14, 2012 4:52 PM, "[email protected]" < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Maxim, >>>>>>> >>>>>>> sounds great! >>>>>>> I currently study some of the upload form components in Wicket. >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2012/10/14 Maxim Solodovnik <[email protected]> >>>>>>> >>>>>>>> >>>>>>>> https://code.google.com/p/red5/issues/detail?id=284&q=label%3AType-Defect >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Sebastian Wagner >>>>>>> https://twitter.com/#!/dead_lock >>>>>>> http://www.webbase-design.de >>>>>>> http://www.wagner-sebastian.com >>>>>>> [email protected] >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Sebastian Wagner >>>>> https://twitter.com/#!/dead_lock >>>>> http://www.webbase-design.de >>>>> http://www.wagner-sebastian.com >>>>> [email protected] >>>>> >>>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >> >> >> >> -- >> Sebastian Wagner >> https://twitter.com/#!/dead_lock >> http://www.webbase-design.de >> http://www.wagner-sebastian.com >> [email protected] >> > > > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
