|
|
Sponsored Content
Special Forums
News, Links, Events and Announcements
Software Releases - RSS News
Growler distributed object architecture 0.3.10 (Default branch)
Post 302197595 by Linux Bot on Wednesday 21st of May 2008 08:40:04 AM
05-21-2008
Growler distributed object architecture 0.3.10 (Default branch)
Growler is a general purpose, C++-based distributed object and event architecture. Though general, its primary application has been in support of collaborative visualization, computational steering, and "concurrent visualization" (the visualization of supercomputer simulations in progress). Growler's distributed object and event architecture is suitable for application to high-performance LAN environments as well the Internet. Its features include strong integration with C++, selective distributed reference counting, and efficient well-typed event channels for local and remote event broadcast.License: OSI ApprovedChanges:A memory usage optimization was made in theobject/event-server component. A race-conditionbug and a buffer-alignment bug which affectedservers were fixed. Several minor bugs were fixed.
More...
|
|
We Also Found This Discussion For You
1. Virtualization and Cloud Computing
Dapper, or "Distributed and Parallel Program Execution Runtime", is a tool for taming the complexities of developing for large-scale cloud and grid computing, enabling the user to create distributed computations from the essentials: the code that will execute, along with a dataflow graph... (0 Replies)
Discussion started by: Linux Bot
0 Replies
LEARN ABOUT LINUX
remote-filesystems
remote-filesystems(7) Miscellaneous Information Manual remote-filesystems(7) NAME
remote-filesystems - event signalling that remote filesystems have been mounted SYNOPSIS
local-filesystems [ENV]... DESCRIPTION
The remote-filesystems event is generated by the mountall(8) daemon after it has mounted all remote filesystems listed in fstab(5). moun- tall(8) emits this event as an informational signal, services and tasks started or stopped by this event will do so in parallel with other activity. This event is typically used by services that must be started to manage remote filesystems. When it occurs, local filesystems such as /usr may not be mounted. For most normal services the filesystem(7) event is sufficient. This event will never occur before the virtual-filesystems(7) event. EXAMPLE
A service that wishes to be running once remote filesystems are mounted might use: start on remote-filesystems SEE ALSO
mounting(7) mounted(7) virtual-filesystems(7) local-filesystems(7) all-swaps(7) filesystem(7) mountall 2009-12-21 remote-filesystems(7)