--- Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote:
> I find this interesting.
> I wonder whether resources should not provide an
> InputStream or something
> like that. Because of selectors.
We are adding getInputStream to Resource. However,
without changing the FileSelector interface (bad), its
ability to interact with Resources is limited. We
could possibly create a new ResourceSelector
interface. If so I'd like to get that nailed down
before I drop this stuff into HEAD, since selectors
are integral to the <restrict> ResourceCollection
type. Do we think a ResourceSelector interface is
necessary? If so, does this tip the scale in favor of
one or more new types subpackages?
Thanks,
Matt
>
> Cheers,
> Antoine
> >
> > --- Matt Benson <[EMAIL PROTECTED]> wrote:
> > > To stay on the same thread, I have been
> developing
> > > in
> > > oata.types . So far I have probably about 15
> > > classes
> > > to add to this package. Any opinions on whether
> we
> > > need oata.types.resource ?
> >
> > or more probably, "resources" so we don't freak
> out
> > Windows for example... :) ?
> > >
> > > -Matt
> > >
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
