123991 - rdf:httpindex should not be tied to xul directory viewer

Status: RESOLVED WONTFIX

(Core Graveyard :: Networking: FTP, defect)

Description

[Doug Turner (:dougt)]

FTP protocol should not change output based on preference.  Instead there should
be a programmatic way that each ftp channel can have a different output.  

There is a new requirement that a client needs to be able to product a listing
of all files in a directory.  To do this, the client wants to parse
indexed-html.  However, if the preference is set, the client will have no way of
knowing how to parse the output.

Comment 1

[Bradley Baetz (:bbaetz)]

dougt: I have about 5 bugs on me because of this, and related code. I was going
to move the html code choice into the channels. I should have a patch later
today for that.

I agree that this is all a hack, but requiring every single consumer who may get
an ftp directory listing back (ie most of them) to change isn't going to work.
What were you proposing to do? See discussion in the related bugs before responding.

Who wants to parse the raw http-index-format, and why? I've always wanted to get
rid of that middle layer entirely - it would make things a _lot_ simpler
thoughout the dir passing code. I even had it working, but valeski wanted to old
stuff kept in.

Comment 2

[Doug Turner (:dougt)]

Bradley could you marked this as a dup?

Comment 3

[Charles Manske]

We need this for Composer's publishing feature. A way of easily enumerating 
files and directories would really help us make a good site viewer/dir picker.

Comment 4

[Bradley Baetz (:bbaetz)]

No, this particular request is slightly different. It'll be one patch which
fixes them, though.

Comment 5

[Doug Turner (:dougt)]

over to bbaetz.

Comment 6

[Bradley Baetz (:bbaetz)]

OK, I'm going to work on this as part of bug 110760. I spoke to cmanske on IRC,
and being able to use the rdf:httpindex datasource will give him what he needs,
so I'm morphing this. This is dependant on bug 110760, which involves moving the
backend out of libappcomps.

This can already be done, sort of, by creating an HTTPIndex instance directly.
That functionality isn't really exposed, though, and editor shouldn't be
dependant on libappcomps.

This will probably be a streight copy and paste, although it was suggested on
IRC that nsIRemoteRDFDataSource should be implemented, and I'll probably do that.

Taking for 0.9.9, but that may be optimistic, since I start university again
next week, and am likely to be very busy until the tree closes.

Comment 7

[Charles Manske]

Thank you Bradley! We will be very happy if you can do this work.

Comment 8

[Bradley Baetz (:bbaetz)]

->1.0

Comment 9

[Bradley Baetz (:bbaetz)]

For when I come to do this, can you please point me to the code where you'd like
to hook this in, so that I can try to have a usable set of APIs?

Comment 10

[Bradley Baetz (:bbaetz)]

Not needed for 1.0; -> 1.1

Comment 11

[Bradley Baetz (:bbaetz)]

cmanske: Is this still wanted in the short term? And if so, can I assign it to
you ;)

Comment 12

[Charles Manske]

No, it's not needed short term. You can keep it!

Comment 13

[Bradley Baetz (:bbaetz)]

I have no time to work on mozilla at the moment, so dougt is taking over FTP

open ftp bugs -> him

Comment 14

[Doug Turner (:dougt)]

mass reassigning to nobody.