Adaptive Overlays for Shared Stream Processing Environments


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Adaptive Overlays for Shared Stream Processing Environments
# 1  
Old 10-07-2008
Adaptive Overlays for Shared Stream Processing Environments

HPL-2007-178 (R.1) Adaptive Overlays for Shared Stream Processing Environments - Papaemmanouil, Olga; Basu, Sujoy; Banerjee, Sujata
Keyword(s): stream processing, overlay, quality-of-service
Abstract: Large-scale overlays has become a powerful paradigm for deploying stream processing applications in wide-area environments. The dynamic nature of these systems makes it difficult to guarantee the Quality of Service (QoS) requirements of each application. In this work we present a framework for distr ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Programming

Shared library with acces to shared memory.

Hello. I am new to this forum and I would like to ask for advice about low level POSIX programming. I have to implement a POSIX compliant C shared library. A file will have some variables and the shared library will have some functions which need those variables. There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies

2. Shell Programming and Scripting

[Video stream] network stream recording with mplayer

Hi I used this command: mplayer http://host/axis-cgi/mjpg/video.cgi -user root -passwd root \ -cache 1024 -fps 25.0 -nosound -vc ffh264 \ -demuxer 3 -dumpstream -dumpfile output.avi It's ok but... Video Playing is very fast! Why? Is it a synch problem? What parameter I have to use for... (1 Reply)
Discussion started by: takeo.kikuta
1 Replies

3. Shell Programming and Scripting

gpsd, gpspipe NMEA sentences stream processing

Hi, running gpsd, gpspipe I get a stream of NMEA sentences. What I need is to write awk script for pipelining and on-the-fly processing of the streamed NMEA senteces to output (terminal session in my case). The issue is, I can get gpsd working in -D 5 mode (debug mode). There is no issue... (5 Replies)
Discussion started by: darius2
5 Replies
Login or Register to Ask a Question
Mojo::IOLoop::Stream(3pm)				User Contributed Perl Documentation				 Mojo::IOLoop::Stream(3pm)

NAME
Mojo::IOLoop::Stream - Non-blocking I/O stream SYNOPSIS
use Mojo::IOLoop::Stream; # Create stream my $stream = Mojo::IOLoop::Stream->new($handle); $stream->on(read => sub { my ($stream, $chunk) = @_; ... }); $stream->on(close => sub { my $stream = shift; ... }); $stream->on(error => sub { my ($stream, $err) = @_; ... }); # Start and stop watching for new data $stream->start; $stream->stop; DESCRIPTION
Mojo::IOLoop::Stream is a container for I/O streams used by Mojo::IOLoop. EVENTS
Mojo::IOLoop::Stream can emit the following events. "close" $stream->on(close => sub { my $stream = shift; ... }); Emitted safely if the stream gets closed. "drain" $stream->on(drain => sub { my $stream = shift; ... }); Emitted safely once all data has been written. "error" $stream->on(error => sub { my ($stream, $err) = @_; ... }); Emitted safely if an error happens on the stream. "read" $stream->on(read => sub { my ($stream, $chunk) = @_; ... }); Emitted safely if new data arrives on the stream. "timeout" $stream->on(timeout => sub { my $stream = shift; ... }); Emitted safely if the stream has been inactive for too long and will get closed automatically. "write" $stream->on(write => sub { my ($stream, $chunk) = @_; ... }); Emitted safely if new data has been written to the stream. ATTRIBUTES
Mojo::IOLoop::Stream implements the following attributes. "reactor" my $reactor = $stream->reactor; $stream = $stream->reactor(Mojo::Reactor::Poll->new); Low level event reactor, defaults to the "reactor" attribute value of the global Mojo::IOLoop singleton. "timeout" my $timeout = $stream->timeout; $stream = $stream->timeout(45); Maximum amount of time in seconds stream can be inactive before getting closed automatically, defaults to 15. Setting the value to 0 will allow this stream to be inactive indefinitely. METHODS
Mojo::IOLoop::Stream inherits all methods from Mojo::EventEmitter and implements the following new ones. "new" my $stream = Mojo::IOLoop::Stream->new($handle); Construct a new Mojo::IOLoop::Stream object. "close" $stream->close; Close stream immediately. "handle" my $handle = $stream->handle; Get handle for stream. "is_readable" my $success = $stream->is_readable; Quick non-blocking check if stream is readable, useful for identifying tainted sockets. "is_writing" my $success = $stream->is_writing; Check if stream is writing. "start" $stream->start; Start watching for new data on the stream. "stop" $stream->stop; Stop watching for new data on the stream. "steal_handle" my $handle = $stream->steal_handle; Steal handle from stream and prevent it from getting closed automatically. "write" $stream->write('Hello!'); $stream->write('Hello!', sub {...}); Write data to stream, the optional drain callback will be invoked once all data has been written. SEE ALSO
Mojolicious, Mojolicious::Guides, <http://mojolicio.us>. perl v5.14.2 2012-09-05 Mojo::IOLoop::Stream(3pm)