Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Java NIO standard options available in fs.open() #306

Open
botic opened this issue Oct 21, 2015 · 3 comments
Open

Make Java NIO standard options available in fs.open() #306

botic opened this issue Oct 21, 2015 · 3 comments

Comments

@botic
Copy link
Member

botic commented Oct 21, 2015

The Java NIO API provides useful standard open options[1] for file operations. At the moment Ringo only supports READ, WRITE, APPEND. Ringo could also provide shortcuts / options for CREATE, CREATE_NEW, DELETE_ON_CLOSE, SPARSE, TRUNCATE_EXISTING.

[1] http://docs.oracle.com/javase/7/docs/api/java/nio/file/StandardOpenOption.html

@botic botic changed the title Make standard options available in fs.open() Make Java NIO standard options available in fs.open() Oct 21, 2015
@kmfdm1
Copy link
Contributor

kmfdm1 commented Oct 21, 2015

Would be nice, but if it isn't supported in common js, we should provide it
in some other way. On the other side: if it doesn't brake the standard,
why not...
Am 21.10.2015 5:14 nachm. schrieb "Philipp Naderer" <
notifications@github.com>:

The Java NIO API provides useful standard open options[1] for file
operations. At the moment Ringo only supports READ, WRITE, APPEND. Ringo
could also provide shortcuts / options for CREATE, CREATE_NEW,
DELETE_ON_CLOSE, SPARSE, TRUNCATE_EXISTING.

[1]
http://docs.oracle.com/javase/7/docs/api/java/nio/file/StandardOpenOption.html


Reply to this email directly or view it on GitHub
#306.

@grob
Copy link
Member

grob commented Oct 21, 2015

👍 these would be just additional options, so i don't see any harm offering them.

@kmfdm1
Copy link
Contributor

kmfdm1 commented Oct 21, 2015

Then it will be a useful addition. We should give a hint in the
documentation that these aren't standard, tough.
Am 21.10.2015 8:15 nachm. schrieb "Robert Gaggl" notifications@github.com:

[image: 👍] these would be just additional options, so i don't see any
harm offering them.


Reply to this email directly or view it on GitHub
#306 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants