14,152 research outputs found
SAMP, the Simple Application Messaging Protocol: Letting applications talk to each other
SAMP, the Simple Application Messaging Protocol, is a hub-based communication
standard for the exchange of data and control between participating client
applications. It has been developed within the context of the Virtual
Observatory with the aim of enabling specialised data analysis tools to
cooperate as a loosely integrated suite, and is now in use by many and varied
desktop and web-based applications dealing with astronomical data. This paper
reviews the requirements and design principles that led to SAMP's
specification, provides a high-level description of the protocol, and discusses
some of its common and possible future usage patterns, with particular
attention to those factors that have aided its success in practice.Comment: 12 pages, 3 figures. Accepted for Virtual Observatory special issue
of Astronomy and Computin
IVOA Recommendation: SAMP - Simple Application Messaging Protocol Version 1.3
SAMP is a messaging protocol that enables astronomy software tools to
interoperate and communicate.
IVOA members have recognised that building a monolithic tool that attempts to
fulfil all the requirements of all users is impractical, and it is a better use
of our limited resources to enable individual tools to work together better.
One element of this is defining common file formats for the exchange of data
between different applications. Another important component is a messaging
system that enables the applications to share data and take advantage of each
other's functionality. SAMP builds on the success of a prior messaging
protocol, PLASTIC, which has been in use since 2006 in over a dozen astronomy
applications and has proven popular with users and developers. It is also
intended to form a framework for more general messaging requirements
HTTP Mailbox - Asynchronous RESTful Communication
We describe HTTP Mailbox, a mechanism to enable RESTful HTTP communication in
an asynchronous mode with a full range of HTTP methods otherwise unavailable to
standard clients and servers. HTTP Mailbox allows for broadcast and multicast
semantics via HTTP. We evaluate a reference implementation using ApacheBench (a
server stress testing tool) demonstrating high throughput (on 1,000 concurrent
requests) and a systemic error rate of 0.01%. Finally, we demonstrate our HTTP
Mailbox implementation in a human assisted web preservation application called
"Preserve Me".Comment: 13 pages, 6 figures, 8 code blocks, 3 equations, and 3 table
XMPP and iDTV or how to make television a social medium
Instant Messaging (IM) has the potential to become one of the killer applications for interactive Digital Television (iDTV) [12]. However, several factors make it difficult to provide a good implementation of IM services, among which the limited resources of a set-top box and the different user experience compared to computer environments.
This paper proposes the XMPP (Extensible Messaging and Presence Protocol) standard as a solution for implementing IM. When we compare XMPP with other technologies, it reveals itself to be very well adapted to the specific needs of iDTV middleware platforms like the Multimedia Home Platform (MHP) [5].
Moreover, the use of XMPP doesn't limit itself to IM The flexible architecture of XMPP opens a window of opportunities like the ease of adding new interactive services. To demonstrate the possibilities of XMPP on MHP, an IM client -IM4MHP- is presented in this paper
A gentle transition from Java programming to Web Services using XML-RPC
Exposing students to leading edge vocational areas of relevance such as Web Services can be difficult. We show a lightweight approach by embedding a key component of Web Services within a Level 3 BSc module in Distributed Computing. We present a ready to use collection of lecture slides and student activities based on XML-RPC. In
addition we show that this material addresses the central topics in the context of web services as identified by Draganova (2003)
- âŠ