006b319c3a
A tool to synchronize objects: Objects derived from AISyncClient can signal that they are 'ready' or 'not ready' for up to 4 events (using a bitmask) at a time. Clients that signal to be ready for anything at roughly the same time as other clients, and which return the same 'hash' (a virtual function returning a 64bit value) will be grouped together and receive events (by means of virtual functions being called) to notify them of all clients being ready or not for one of the events (syncevent1). The other three events can be polled. The memory usage is low (one pointer per client that points to its AISyncServer object), servers are released to a cache after about 100 ms (unless there is actual need for synchronization), so there aren't much of those either. The CPU usage is extremely low: all events are handled in parallel in a 32 bit value (6 bits per event to count the number of registered clients and the number of ready clients for each event, and the remaining 8 bits to count the number of reference pointers (which should only be a constant higher, so that is overkill). To signal to a server that a client has become ready or not is mostly a function call, which then takes 1 clock cycle or so before returning. Registration of a client is slightly more expensive as it requires a pointer to be added to the end of a std::list. This tool could easily be used as part of the graphics engine (not that I intend to do that :p).
00000000011111111112222222222333333333344444444445555555555666666666677777777778
12345678901234567890123456789012345678901234567890123456789012345678901234567890
______ ___ __ _ _____ _ _ ______ _____ ___ _____ _ _
|_____ | | \ | | ___ | | | |____| |____/ | | \_/
_____| _|_ | \_| |____| |____| |____ | | | \_ _|_ | |
_ _ _ ____ _ _ ____ ____
\/ | |=== |/\| |=== |--<
Sin-gu-la-ri-ty (noun) - a distinctive feature, a uniqueness; a point at which
continuity breaks up; a point in history at which machine becomes smarter than
humanity and/or fuses with it indivisively; or simply a cool sounding word with
the initials S.G. in it :)
Singularity Viewer is a SecondLife(tm) protocol compatible client application.
It can be used to access SecondLife services as well as a number of others such
as those based upon the OpenSim platform.
Singularity is maintained by a small group of volunteers who can be contacted
both, in-world (SingularityViewer group) as well as on IRC (#SingularityViewer
@ FreeNode). Bug requests and features requests can be submitted through our
Issue Tracker (http://code.google.com/p/singularity-viewer/issues/list or from
the viewer menu: Help --> Bug Reporting --> Singularity Issue Tracker...)
As this Readme grows out of date, please refer to
http://www.singularityviewer.org/about
00000000011111111112222222222333333333344444444445555555555666666666677777777778
12345678901234567890123456789012345678901234567890123456789012345678901234567890
History
The Singularity viewer was started by Siana Gearz in November 2010 by forking it
from the Ascent Viewer, by Balseraph Software Group, which in turn was based upon
source code modified from the snowglobe source code released by Linden Lab.