Jefry has sent me a patch. I'll work to process it soon.
On 11/28/11 3:07 PM, Jefry Lagrange wrote: > Thanks for your response. ;-) > >> I'm not sure it's a good idea to overload the disco request this way. >> Perhaps having the filter in a separate namespace would be ok, but I >> think perhaps it would be better to use another protocol for this. > > > Yeah, I wasn't sure about it either. But this way is at least > consistent with what the XEP says about asking for file information. > > The XEP currently uses disco requests extensively in section 4 and 5. > If disco overuse is a problem, wouldn't it be better to stop using it > in those sections as well? > > Alternatively we could use a new stanza, like <match> </match>, with a > new namespace. But it wouldn't be consistent. We would want to keep > "requesting file list" and "requesting file information", within the > same namespace as "finding specific files". > > The filter I propose has no new elements. Everything is reused from > XEP-122. A new extension for it would be small, and it wouldn't > contain new information. > > > Cheers, > > On Mon, Nov 28, 2011 at 9:41 AM, Matthew Wild <mwi...@gmail.com> wrote: >> On 27 November 2011 03:50, Jefry Lagrange <jefry.re...@gmail.com> wrote: >>> Hi, I been working on some changes to XEP-0135. >>> >>> * Replacing SI file transfer with jingle FT >> >> Good :) >> >>> * Replacing section 6, with a link pointing to section 5 of XEP-0234, >>> which already covers the same function. >> >> Makes sense. >> >>> * Adding support for pubsub, only for finding files using the method I >>> introduce bellow. It doesn't make much sense to traverse the directory >>> of every user subscribed to a pubsub, but it will make a lot of sense >>> searching for specific files. (XEP-0137 does not suffice for this) >> >> Agreed. >> >>> 5.5 Finding Specific Files >>> >>> Finding files by asking for a file list is not very practical if there >>> are too many files being shared. It is very resource intensive and it >>> is understood that the user may not be interested in all of the files, >>> but rather he or she would be interested in finding one specific file >>> or one specific kind of file (text, image or videos). >>> >>> In order to do this, the identity stanza is used to match files by one >>> or more fields i.e. 'name', 'date', 'size', etc... >>> >>> Example XX. Finding Specific Files >>> >>> <iq type='get' >>> from='ha...@shakespeare.lit/pda' >>> to='darkc...@shakespeare.lit' >>> id='find45'> >>> <query xmlns='http://jabber.org/protocol/disco#info' >>> node='files'> >>> <identity category='filesys' type='file' name='file1' /> >>> </query> >>> </iq> >>> >> >> I'm not sure it's a good idea to overload the disco request this way. >> Perhaps having the filter in a separate namespace would be ok, but I >> think perhaps it would be better to use another protocol for this. >> >>> Example XX. Finding files using Regular Expressions >>> >> >> Another useful feature, but I even more strongly feel this shouldn't >> be done over disco. >> >>> Any feedback would be greatly appreciated, I just want to know if I am >>> on the right track here. >> >> Absolutely, I'd love to see this spec revived. I look forward to >> seeing a new XEP draft :) >> >> Regards, >> Matthew >>
