Growler distributed object architecture 0.3.9 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Growler distributed object architecture 0.3.9 (Default branch)
# 1  
Old 02-24-2008
Growler distributed object architecture 0.3.9 (Default branch)

Image 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 Approved Changes:
Python bindings were added for some parts of Growler. Rotation and scaling were added for 3x3 matrices. Bugs were fixed in buffer management, mainly for infiniband. Other minor bugs were fixed.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Dapper Distributed Dataflow Engine 0.91 (Default branch)

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
Login or Register to Ask a Question
arch(1) 							   User Commands							   arch(1)

NAME
arch - display the architecture of the current host SYNOPSIS
arch [-k | archname] DESCRIPTION
The arch utility displays the application architecture of the current host system. Due to extensive historical use of this command without any options, all SunOS 5.x SPARC based systems will return "sun4" as their application architecture. Use of this command is discouraged. See NOTES section below. Systems can be broadly classified by their architectures, which define what executables will run on which machines. A distinction can be made between kernel architecture and application architecture (or, commonly, just "architecture"). Machines that run different kernels due to underlying hardware differences may be able to run the same application programs. OPTIONS
-k Displays the kernel architecture, such as sun4u. This defines which specific SunOS kernel will run on the machine, and has implica- tions only for programs that depend on the kernel explicitly (for example, ps(1)). OPERANDS
The following operand is supported: archname Use archname to determine whether the application binaries for this application architecture can run on the current host sys- tem. The archname must be a valid application architecture, such as sun4, i86pc, and so forth. If application binaries for archname can run on the current host system, TRUE (0) is returned. Otherwise, FALSE (1) is returned. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
mach(1), ps(1), uname(1), attributes(5) NOTES
This command is provided for compatibility with previous releases and its use is discouraged. Instead, the uname command is recommended. See uname(1) for usage information. SunOS 5.11 21 Oct 2002 arch(1)