Hyperactive Resource 0.1 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Hyperactive Resource 0.1 (Default branch)
# 1  
Old 07-29-2008
Hyperactive Resource 0.1 (Default branch)

HyperactiveResource extends ActiveResource (from Ruby on Rails) to provide a REST client library that behaves like ActiveRecord. Features include client side validations, hooks for before_validate, before_save, dynamic finders, save!, awareness of associations between resources, the ability to associate resources with records and vice versa, and saving resources that :include other resources.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

Resource Capping Help!

Hi guys. Quick question for some hopefully ;-) When using resource capping (for CPU in this case). If a container is restricted to use a single CPU/core, are the other containers intelligent enough to know that they have fewer CPU's available to them? My question relates to a T2000 which... (7 Replies)
Discussion started by: boneyard
7 Replies

2. Solaris

need some help in resource pool creation

i have server carry more than 50 zone i want to create 2 resource pool assign 40 zone to resource pool number 1 assign 10 zone to resource pool number 2 how can i do that (1 Reply)
Discussion started by: coxmanchester
1 Replies

3. UNIX for Dummies Questions & Answers

Device or resource busy??

Hi, I'm trying to do a sharity mount to mount a terastation network drive. I'm getting a Device or resource busy message after my mount command. Please see output below... # /usr/local/sharity3/bin/sharity mount smb://labbackup01/bakup_data /mnt/labbackup01 Device or resource busy.... (2 Replies)
Discussion started by: orahi001
2 Replies

4. AIX

Resource Manager in AIX

Hi all, I am a newbie to AIX. Can any one give me any idea of resource manager in AIX. How can i use it to schedule jobs at appropriate times. Any pointers to tutorials will b of great help. (4 Replies)
Discussion started by: snail2santosh
4 Replies

5. Solaris

resource worries

When I run the prstat -a command I get the following output for user oracle. NPROC USERNAME SIZE RSS MEMORY TIME CPU 118 oracle 70G 30G 100% 4:38:03 52% The reading under the "MEMORY" heading is 100%. What does this mean? I hope it doesn't mean user oracle is using... (2 Replies)
Discussion started by: soliberus
2 Replies

6. Linux

Resource management

Hi all, we have a big problem, we are running an IA-64 linux system, with 8 CPUs and some GB of RAM, for user usage. The user are compiling and testing programs on this system, and this caused some problems. Sometimes, a user program used the hole memory, blocks the other users, and also... (1 Reply)
Discussion started by: malcom
1 Replies

7. UNIX for Dummies Questions & Answers

resource manaement

Hi all I would like to know which other tools i can use besides top & sar to track the system resources i heard of somthing that sounds like acamdmin or acsadm... Thanks for your help (1 Reply)
Discussion started by: yelalouf
1 Replies
Login or Register to Ask a Question
oss_midiloop(7) 						    OSS Devices 						   oss_midiloop(7)

NAME
oss_midiloop - Loopback MIDI driver. DESCRIPTION
The loopback midi driver makes it possible to create special purpose virtual midi devices based on user land server processes. INTRODUCTION
MIDI loopback devices are like named pipes or pseudo terminals. They are grouped in client and server device pairs. The server side device must be open before the client side device can be opened. SERVER SIDE DEVICE The server side device is used by some special application (such as a software based MIDI synthesizer) to receice MIDI events from the applications that want to play MIDI. CLIENT SIDE DEVICE Client applications such as MIDI players open the client side device when they need to play some MIDI stream (file). The client side device behaves like any "ordinary" MIDI device. However it cannot be opened when there is no program connected to the server side. COMPATIBILITY ISSUES
MIDI loopback devices differ from "normal" MIDI devices because an application is needed at the both ends of the loop. The loop device will return a "Connection reset by peer" error (ECONNRESET) error. Applications designed to be used as loopback based server applications can/should use this error (returned by read or write) as an end-of-stream indication. OPTIONS
o midiloop_instances: Specifies how many loopback client/server MIDI device pairs to be created. Values: 1-16 Default: 1 KNOWN PROBLEMS
None FILES
/etc/oss4/conf/oss_midiloop.conf Device configuration file AUTHOR
4Front Technologies 16 December 2012 oss_midiloop(7)