SERVAL SYSTEM

Internet services provided clients with access to the resources of a particular host. However, today’s services are no longer defined by a single host or confined to a fixed location. Yet, the network architecture continues to impose an unfortunate coupling between hosts and services by binding connections to topology-dependent addresses, rather than topology-independent service names—complicating everything from server replication, load balancing, and virtual machine migration, to client mobility and multi-homing.

Open serval system is what Assistant Professor of Computer Science Michael Freedman calls a Service Access Layer that sits between the IP Network Layer (Layer 3) and Transport Layer (Layer 4), where it can work with unmodified network devices. Serval's purpose is to make Web services such as Gmail and Facebook more easily accessible, regardless of where an end user is, via a services naming scheme that augments what the researchers call an IP address set-up "designed for communication between fixed hosts with topology-dependent addresses." Data center operators could benefit by running Web servers in virtual machines across the cloud and rely less on traditional load balancers.

The Shared Access Layer, or SAL for short, provides a consistent, cohesive API to common plugin tasks, regardless of the Atlassian application into which your plugin is deployed. SAL is most useful for cross-application plugin development. If you are developing your plugin for a single application only, you can simply use the application's own API. If your plugin will run in two applications or more, you will find SAL's services useful. These common services include, but are not limited these.