Mono 2.4.1 fixes most of them including the RPC issue. But there are certain other exceptions when we scale to 20k users. We are trying our best to make sure this update to trunk will have very good non-functional parameters.
Kalis >>> On 5/24/2009 at 9:26 PM, in message <gvbquq$qn...@ger.gmane.org>, "Andrés G. Aragoneses"<kno...@gmail.com> wrote: > Balakrishnan KalIdas wrote: > > Hi All, > > > > Just providing certain updates on what is happening. > > > > Newer-Mono > > ~~~~~~~~~~ > > There are few exceptions we are facing with the newer mono. We are > constantly working with Mono folks to get it running. Hopefully we will have > the trunk fixed soon for newer mono. > > I sent a message some days ago summarizing the problems with iFolder > with the last Mono version released (2.4.0). I'm attaching them to this > message again? Is the list missing some item? Because, as I already > stated on it, all seems to be fixed already with Mono 2.4.1 (which > hasn't been released yet). > > > > The SOAP RPC mechanism is changed and that is another reason why the > clients and server fail to communicate - we are trying to work-around this. > > What's the bug number of this? I have no issues using iFolder trunk and > Mono 2.4.1. > > Thanks, > > Andres > > > > Once we get our fixes ready, we will update the source with the > consolidated fix, so that we do not break the current trunk. > > > > New UI > > ~~~~~~~ > > New UI effort is also going on in a separate branch in parallel - to make > iFolder look and feel much better and add more usability. > > > > The UI folks will update the list on when the code will be compilable and a > usable UI is available for more feedback. > > > > Kalis > > _______________________________________________ > ifolder-dev mailing list > ifolder-dev@forge.novell.com > http://forge.novell.com/mailman/listinfo/ifolder-dev _______________________________________________ ifolder-dev mailing list ifolder-dev@forge.novell.com http://forge.novell.com/mailman/listinfo/ifolder-dev
