Closed Bug 244571 Opened 20 years ago Closed 9 years ago

Support for multiple open sockets to push/pull files from Roaming store

Categories

(Core Graveyard :: Profile: Roaming, enhancement)

x86
Linux
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jmccabe, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040524 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040524 Currently the Roaming Profile transfers files synchronously (start transfer for file foo, wait for completion, begin transfer for file bar, wait for completion, etc). It would be a huge boon to have Moz open multiple connections to the server. Reproducible: Always Steps to Reproduce:
> It would be a huge boon to have Moz open multiple connections to the server. Why? Esp. if you're bandwidth-limited (as you probably are with servers on the Internet, which you said you use), it shouldn't make much of a difference, does it? There is explicit code to transfer in parallel, see <http://lxr.mozilla.org/seamonkey/source/extensions/sroaming/resources/content/transfer/transfer.js#61> (Comment at the top) <http://lxr.mozilla.org/seamonkey/source/extensions/sroaming/src/Stream.cpp#218> (Comment and |ioParamBlock->SetInt(1, 2);| in Stream::DownUpLoad()) I just didn't think that there is a good and frequent reason to do that, so I didn't implement a way to set this setting (in the Mozilla registry), but hardcoded it. If you wanted to implement this, you just need to change Stream.cpp and add a registry value like the existing |SavePassword|. I don't see enough use for it to have UI, though, so I don't know how you'd change the Mozilla registry as a user. If you want to hack it in your copy of Mozilla, open transfer.js in sroaming.jar and change this.serial = serial; (currently like 99) to this.serial = false; Of course, any warranty is void, if you remove the seal like this ;-).
Status: UNCONFIRMED → NEW
Ever confirmed: true
> ioParamBlock->SetInt(1, 2); Actually, it seems there is a bug somewhere. 2 (which I use here) is defined as parallel, not serial, but it seems we do transfer serially, not in parallel. (Yeah, magic numbers :-(. Because of nsIDialogParamBlock.)
Assignee: nobody → ben.bucksch
Component: Profile: BackEnd → Profile: Roaming
QA Contact: core.profile-manager-backend → core.profile-roaming
Assignee: ben.bucksch → nobody
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.
No longer blocks: 1243899
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.