Community
Participate
Working Groups
Bug 348915 failed to fix the problem; the problem is that the message is logged, not that it's an info/warning. This is causing unnecessary noise in the log for people who just want to use ECF. We don't want to see adverts of "Enjoyed ECF's sync services? You may also want to look into Async services, available in the foyer now!"
(In reply to comment #0) > Bug 348915 failed to fix the problem; the problem is that the message is > logged, not that it's an info/warning. This is causing unnecessary noise in the > log for people who just want to use ECF. We don't want to see adverts of > "Enjoyed ECF's sync services? You may also want to look into Async services, > available in the foyer now!" :) Although I'm sympathetic to the 'noise' question...and willing to remove the message given an approach that allows flexibility (as you described on another bug)...I don't really think that over-promotion of ECF's unique remote services features (e.g. async)...or promotion of any of ECF for that matter...is currently our biggest marketing problem. :) Honestly, I'll be happier when it is our biggest marketing problem...so maybe we're getting there ;-)
Message for async proxy removed for ECF 3.5.2. Resolving as fixed.