|normally obtains from a file. For example, take the
|jboss/system/home/db/jbossmq/QUEUE.A.dat29 file as a DirContext and
|there could be the following attributes
|+ QUEUE.A.dat29
|| -- lastModified = Date of last modification
|| -- size = size of file in bytes
|| -- in = java.io.InputStream for reading the file
|| -- out = java.io.OutputStream for writing the file
|| etc.
huh... interesting indeed... this does provide a portable way to access file
systems, local or not... interesting
you are making the "distributed filesystem" view of JNDI I love to rap about
so much a concrete reality.
|Fine for now. However, everyone needs to be thinking about how to limit
|dependency on the filesystem.
If it is truly distributed it is then just a persistent storage view of
things.
That is what the filesystem was and will always be... just a 'persistent
store' on clumsy disks. We abstract that view in something more web
friendly. Once we re-invent the feel of files in the web then we can go
back and say "files ok" but for now you are absolutely right, we need to
limit the usage of the files as people understand "LOCAL FS" which is bad.
marcf
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
