Err. I mean JSR-133.
--Will
Will Pugh wrote:
Look at JSR 166 section 3.5.
sebb wrote:
On 10/10/2007, Will Pugh (JIRA) <[EMAIL PROTECTED]> wrote:
[
https://issues.apache.org/jira/browse/CODEC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wil
Look at JSR 166 section 3.5.
sebb wrote:
On 10/10/2007, Will Pugh (JIRA) <[EMAIL PROTECTED]> wrote:
[
https://issues.apache.org/jira/browse/CODEC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Pugh updated CO
Oliver Zeigermann wrote:
2007/10/3, Will Pugh <[EMAIL PROTECTED]>:
Another idea (not well thought out) would be to try doing something like
threadlets for Java (http://kerneltrap.org/node/7753)
So that some operation would either execute directly, or if a lock is
taken would s
Another idea (not well thought out) would be to try doing something like
threadlets for Java (http://kerneltrap.org/node/7753)
So that some operation would either execute directly, or if a lock is
taken would spawn a thread to wait for access. Not sure if it's a
solution in search of a proble
I wrote some zip writing code for compress that can modify the actual
zip files. I submitted it and then fell off the face of the earth. In
July, I came back an fixed up some of the concerns, but I think the
pause ended up losing some of the interest in this.
http://issues.apache.org/jira/br