I saw some discussion on irc about this when I was headed to bed one night.
So, whats the story morning glory?
On Mon, 2004-05-03 at 11:19 +0800, Not Zed wrote:
This is only an 'issue' because each component hard-codes its component name in its password handling code. In the mailer we can easily add an override component field to our get-password call. This is how i'd suggest it get fixed in all components if possible.
On Sat, 2004-05-01 at 14:41 +0530, Sivaiah N wrote:Hi, Currently we pass uri and component name for e_passwords_ask_password call. Since the component names are different, the password remembered in one component can not be reused in another component even though the server name and user name (user and server names are generally part of the passed in uri )are same (like in case of groupwise). We can pass "Groupwise" as the component name but it requires special handling like checking whether an uri has groupwise prefix or not in all components. can we do something more generic here? Or passing Groupwise as i said above is OK? Thanks, Sivaiah _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
![]()
Michael Zucchi <[EMAIL PROTECTED]>
Ximian Evolution and Free Software Developer
Novell, Inc.
|
<<attachment: zed-48.small.jpg>>
<<attachment: zed-48.small.jpg>>
