gluegen.git - GLUEGEN repository on http://jogamp.org/ ;

	Commit message (Collapse)	Author	Age	Files	Lines
*	gluegen: remove trailing whitespace	Harvey Harrison	2013-10-17	7	-137/+137
\| \| \| \|	Signed-off-by: Harvey Harrison <[email protected]>
*	Fix SingletonInstanceServerSocket.kill(): Needs to mark alive=false in case ↵	Sven Gothel	2013-06-25	1	-1/+1
\| \| \| \|	of JVM shutdown!
*	RecursiveThreadGroupLockImpl01Unfairish: Fix DEBUG output	Sven Gothel	2013-05-05	1	-3/+4
\|
*	Fix RecursiveLockImpl* corner case: Timeout reached but lock released -> ↵	Sven Gothel	2013-03-18	2	-16/+20
\| \| \| \| \| \|	Assume Lock If timeout has been reached but the lock has been released, the lock has to be assumed.
*	gluegen: replace Thread name with name of lock file in ↵	Harvey Harrison	2012-10-16	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \|	SingletonInstanceFileLock error message The getName() call here is currently calling Thread.getName() inherited by the anonymous inner class. This is ambiguous, and likely meant to call the getName() method of SingletonInstanceFileLock, which would output the lockfile name. In any event, infoPrefix() is already adding the Thread name for us. Signed-off-by: Harvey Harrison <[email protected]>
*	SingletonInstanceServerSocket: serverSocket.setReuseAddress(true); // reuse ↵	Sven Gothel	2012-10-04	1	-0/+1
\| \| \| \|	same port w/ subsequent instance, i.e. overcome TO state when JVM crashed
*	SingletonInstanceServerSocket: Add unit tests; Create new server Thread @ ↵	Sven Gothel	2012-09-21	2	-18/+18
\| \| \| \|	start, otherwise we may collide w/ a failed start. Misc: Cleanup / reuse strings.
*	SingletonInstanceServerSocket: Add kill @ JVM Shutdown _and_ if normal ↵	Sven Gothel	2012-09-21	2	-8/+42
\| \| \| \|	unlock fails ; Added unit tests.
*	Lock Cleanup (API Change)	Sven Gothel	2012-06-27	6	-17/+64
\| \| \| \| \| \| \| \|	- LockExt -> ThreadLock - clarifying semantics (API Change) - ThreadLock: Remove isOwner(), use isOwner(Thread.currentThread) - adding @Override
*	StringBuffer -> StringBuilder (Local objects, no concurrency)	Sven Gothel	2012-04-16	1	-1/+1
\|
*	RecursiveThreadGroupLock: New recursive lock interface and impl, allowing ↵	Sven Gothel	2011-12-11	1	-0/+211
\| \| \| \| \| \| \| \| \| \| \| \|	'spawn off' process to become the lock owner. To avoid complicated synchronization via synchronized, wait and notify between one thread and a 'spawn' off thread which temporarly requires the hold lock, RecursiveThreadGroupLock allows to add and remove other threads to become owners of the lock as if they were the original holder. This simplifies some rare locking use cases, eg. in JOGL's GLProfile initialization sequence where a SharedResourceRunner thread is taking over initialization of shared resources.
*	Cleanup Lock Package: API doc, complete throws declaration, interface ↵	Sven Gothel	2011-12-11	3	-43/+83
\| \| \| \| \| \|	RecursiveLockImpl01Unfairish.Sync RecursiveLockImpl01Unfairish changes are in preparation of RecursiveGroupThreadLock.
*	Lock ChangeSet (fin): Cleanup, fix and enhance RecursiveLock implementation	Sven Gothel	2011-09-27	4	-122/+613
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	- RecursiveLock _is_ interface. - Use LockFactory to create a RecursiveLock. - Impl: RecursiveLockImpl01Unfairish - just using notify w/o any queue: fast - still enqueuing new lock-applicants if queue full (nice) - lock's sync extends AbstractOwnableSynchronizer and uses it (monitor) - Impl: RecursiveLockImpl01CompleteFair - using queue and interrupt for correctness (slow) - lock's sync extends AbstractOwnableSynchronizer and uses it (monitor) - Impl: RecursiveLockImplJava5 for using Java5's concurrency impl. - to verify correctness, performance and deviation of locking time TestRecursiveLock01 new performance measurements incl. simple avrg and deviation shows best combined performance-deviation w/ our RecursiveLockImpl01Unfairish os Linux and MacOSX. RecursiveLockImpl01Unfairish is the default in LockFactory. Adding 'private' LockDebugUtil, allowing validating all holdings locks of one thread as stack traces (Throwable). Besides the AbstractOwnableSynchronizer utilization, this helps debugging deadlocks and starvation very well.
*	Lock ChangeSet: Prepare RecursiveLock to be an implementation of it's new ↵	Sven Gothel	2011-09-27	1	-0/+245
\| \| \| \|	interface
*	SingletonInstanceServerSocket: composite thread name w/ leading original one	Sven Gothel	2011-09-25	1	-1/+8
\|
*	SingletonInstanceServerSocket: Fix setDaemon(true), give Thread a proper name	Sven Gothel	2011-06-12	1	-2/+2
\|
*	SingletonInstance Enhancements / Minor Lock/LockExt API Change (isLocked ↵	Sven Gothel	2011-06-11	2	-0/+351
	moved up) We learned that FileChannel.lock() is not reliable on at least GNU/Linux + Sun's JVM implementation, hence we need a ServerSocket implementation. Since this code may be useful to others, it has been promoted to GlueGen. - Abstract SingletonInstance - Implement Lock interface - SingletonInstance Spezialisation: FileLock and ServerSocket Minor API Change: LockExt.isLocked() -> Lock.isLocked()