235744 - Expose StorageStream class to Javascript

Status: RESOLVED FIXED

(Core :: XPCOM, defect)

Description

[Nick Sayer]

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

In order to be able to do form posting conveniently from Javascript, it would be
helpful to expose the StorageStream object.

Reproducible: Always
Steps to Reproduce:
1. in xpcshell
js> Components.classes['@mozilla.org/storagestream;1']

Actual Results:  
Got nothing


Expected Results:  
@mozilla.org/storagestream;1

Comment 1

[Nick Sayer]

Attachment: Proposed patch

Comment 2

[Darin Fisher]

Comment on attachment 142357 [details] [diff] [review]
Proposed patch

r+sr=darin if you make all the '\'-chars line up :)

Comment 3

[timeless]

mozilla/xpcom/build/nsXPComInit.cpp 	1.193
mozilla/xpcom/io/nsStorageStream.h 	1.10

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

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

Comment 5

[timeless]

Attachment: missing interface changes

Comment 6

[Darin Fisher]

Comment on attachment 151044 [details] [diff] [review]
missing interface changes

r+sr=darin

though, it'd be nice if maxSize were replaced with segmentCount instead.  that
is the convention followed by newer similar interfaces in necko and xpcom.

Comment 7

[basic]

not sure where else to ask this, are there any examples on how to use this
"init" interface?

Comment 8

[timeless]

nope, sorry :)
a quick scan seems to indicate that nsMemoryCacheDevice uses init(4096, -1, null).

mozilla/xpcom/io/nsIStorageStream.idl 	1.5
mozilla/xpcom/io/nsStorageStream.h 	1.12
mozilla/xpcom/io/nsStorageStream.cpp 	1.29

sorry about the mess, i totally forgot about the related changes. i just pulled
them from my cvs repository as i ran into them, so they really aren't my changes
(and we made them nearly four months ago).

Comment 9

[basic]

timeless: we need this on 1.7 branch as well?