| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
region crossing or teleport.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
connection failure happens
|
|
response. Still needs work though.
|
|
|
|
character step as the server will now be doing the math.
|
|
|
|
|
|
check the server response in an effort to ensure the viewer and server remain in sync. This is a partial commit as I still need to add user behavior and notifications when things go wrong.
|
|
|
|
|
|
|
|
|
|
change.
|
|
|
|
|
|
|
|
|
|
|
|
case of a teleport failure on the second attempt.
|
|
|
|
|
|
|
|
|
|
access level. But only toggling it in the viewer leads to some really bad discontinuities with the server's actual access level for the user.
|
|
|
|
completely tested
|
|
|
|
This is the first functional viewer pass with the HTTP work of the texture fetch
code performed by the llcorehttp library. Not exactly a 'drop-in' replacement
but a work-alike with some changes (e.g. handler notification in consumer
thread versus responder notification in worker thread).
This also includes some temporary changes in the priority scheme to prevent
the kind of priority inversion found in VWR-28996. Scheme used here does
provide liveness if not optimal responsiveness or order-of-operation.
The llcorehttp library at this point is far from optimally performing.
Its worker thread is making relatively poor use of cycles it gets and
it doesn't idle or sleep intelligently yet. This early integration step
helps shake out the interfaces, implementation niceties will be covered
soon.
|
|
|
|
|
