On Tue, 2009-12-15 at 11:04 -0500, Dale Worley wrote: > On Tue, 2009-12-15 at 09:08 -0500, Scott Lawrence wrote: > > On Mon, 2009-12-14 at 15:19 -0500, Scott Lawrence wrote: > > > > > My thinking is/was that subdirectories should be specified separately, > > > so for example: > > > > > > <directory> > > > <path>/etc/sipxpbx/foo</path> > > > <filepattern>*.xml</filepattern> > > > <filepattern>*.wav</filepattern> > > > </directory> > > > <directory> > > > <path>/etc/sipxpbx/foo/bar</path> > > > <filepattern>*.abc</filepattern> > > > </directory> > > > <directory> > > > <path>/etc/sipxpbx/foo/bingo</path> > > > <filepattern>*.xyz</filepattern> > > > </directory> > > It seems easier to me to do: > > <filepattern>/etc/sipxpbx/foo/*.xml</filepattern> > <filepattern>/etc/sipxpbx/foo/*.xml</filepattern> > <filepattern>/etc/sipxpbx/foo/bar/*.abc</filepattern> > <filepattern>/etc/sipxpbx/foo/bingo/*.xyz</filepattern>
Yes, but the additional primitive I'd also like to add is one to get a list of what files are in a directory (which, in fairness, I had not mentioned), so I'd like to have the directory path itself access controlled. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
