Subpart of bug #17048. Implement the client side of the ACAP protocol for roaming access.

ops.

Adding dependency on bug 28200 since the ACAP protocol needs SASL.

that doesn't make sense - that other bug is to use SASL in IMAP. What I think you're looking for is a bug to create a SASL interface in mozilla.

mass move, v2. qa to me.

ACAP blocking all of Roaming seems a bit extreme - can we agree that ACAP isn't the only form of gathering personal user information for mozilla config? Can we perhaps attempt a simpler http (even simpleput) roaming setup first, then move to the entirely new (as in Nothing Like We've Done Before) protocol? I'm sure a pro-LDAP-Roaming mind will probably speak up, there seems to be a well-established Apache+Roaming bunch of admins that would stop mewling so much if that minimal functionality were achieved.

Bishop: Bug 17048 is a meta bug. It also has a dependency on bug 18043, which is for roaming through HTTP or FTP.

Pro-LDAP-roaming mind speaking up! :) I argee with Bishop. Get the initial bare-bones HTTP roaming access code in there first, then put in LDAP support, then ACAP. (What's ACAP anyway?) There's still a few features left from Netscape that need to be ported over to Mozilla, support for various LDAP features (like this and address books) being a major chunk of those.

ACAP is the Application Configuration Access Protocol. It's sort of like IMAP, but for application prefs instead of mail.

I agree to get the roaming working first on HTTP and LDAP (like what Netscape 4.x does). Right now, no roaming is really a problem when using several computers. The code is somewhere in Netscape 4.x, isn't there a way to cut & paste it into mozilla to get some basic functionality there. I don't have much time, but I can try to contribute some of my time if somebody can provide me with the existing code.

Changing dependency from blocking to depends. Nobody is holding back roaming because ACAP would be too hard. No, the 4.x code is too different to be useful (or so I'm told).

The code is probably good guidance in terms of looking at how to do roaming. I often wonder how mature the feature was, because when I tried to implement the Comm 4 version, I found lots of annoying little things happened that weren't documented, for example redirects.

*** Bug 218423 has been marked as a duplicate of this bug. ***

shouldn't this bug be more general than just "browser"? It is also related to mail/news and thunderbird.

Browser is the core component. Eventually the products may be renamed, but until then if you don't know or understand the bugzilla product organization you probably shouldn't comment into bugzilla with questions like "shouldn't this be ...". For help understanding bugzilla you might try #mozillazine on irc.mozilla.org

(Keep summary concise) Note <http://lxr.mozilla.org/seamonkey/source/extensions/sroaming/README.txt>, first paragraph: "To make the implementation vastly more simple, it has been decided that no syncing during the session happens. The design will not allow that either (at most sync in certain intervalls). A full-blown dynamic implementation that immediately update the server when a data change occured requires the cooperation of the data providers (bookmarks, prefs etc.) and is thus a huge change that I will leave to somebody else to implement independant of this roaming support here." Bug 245985 could reduce the impact a little, but not fully.

To help answer the question "What's ACAP?" that Brendan Byrd asked, here are some links to the ACAP resources I have found most useful: http://dave.cridland.net/acap/ http://www.defendmail.sunet.com.au/Projects/ACAP/ [Disclaimer; I wrote this yonks ago, when I knew 0 about Mozilla] As to why you'd want to use it, this is exactly what ACAP was created for, so in theory it should be easy :).

I think at this point ACAP has been usurped by WebDAV.

Maybe it has been usurped by WebDAV, but have you discovered that big pliers make a passable hammer? :) I say we find the right tool for the job, and then give people the option to use any tool they want. I guess my point is, once we get the universal preferences API (see links below) then ACAP should be easy to implement. http://wiki.mozilla.org/wiki/Mozilla2:Unified_Storage http://wiki.mozilla.org/wiki/Mozilla2:Multi_User_Sharing

In light of the most recent comment on the SASL bug blocking this one, does that mean that it doesn't need to block this one any more?

ACAP is dead.. long live WebDAV.

I'm with Alec here, since WebDAV is well-understood and widely deployed.

This bug is filed in a bugzilla component related to pre-Firefox code which no longer exists. I believe it is no longer relevant and I am therefore closing it INCOMPLETE. If you believe that this bug is still valid and needs to be fixed, please reopen it and move it to the Toolkit:Startup and Profile System product/component.