Free trip software for linux

JumpBox vTiger CRM project is a JumpBox virtual appliance with a pre-configured installation of the vTiger CRM system.

Once upon a time, in the raw and exciting days when automobile technology was in its infancy, taking a road trip meant bringing a mechanic along to fix the car every time it broke down. At JumpBox we look at the current state of IT systems and see great similarity with the early automobile.

Today, if you want to deploy and run a server based application you need a mechanic to come along to keep it running. With the automobile, as time passed, the technology improved, cars became vastly more reliable and many more people were able to take to the road.

With JumpBox we’re looking to do the same for server based software. We simplify what has traditionally been complex and deliver server based Open Source applications to an audience that otherwise would be put off by the technical burdens of the old way of doing things.

An integrated software stack in a virtual appliance

A JumpBox bundles the operating system, application and all application dependancies into a single installable module that’s easily deployed using virtualization software from VMWare, Parallels or Xen

Easy to Install

A JumpBox allows you to install a complex server based application without having to know anything about Linux, databases or the command line. You just download, extract the archive and open the application with your virtualization software. Further setup and configuration is handled through a simple web interface.

Simple to manage

The JumpBox platform is pre-configured, tuned and secured to minimize the management needs of the application.

Runs anywhere

Mac OS X, Linux, Windows it doesn’t matter. Thanks to the use of virtualization, JumpBox applications run easily on all the most popular operating systems.

Painless to upgrade

With a JumpBox and the JumpBox Assurance program (launching Q2 2007), management of the system is simple and efficient. Updates to the entire software stack are handled automatically by the platform with minimal user interaction.

Quick to move

With a JumpBox all the application code, data and the runtime are bundled together into a single directory that can easily be moved between systems or even across platforms. This allows you to start using an application by just running it on your desktop. Then when you’re ready you can open it up to the rest of the network and either continue running it on your desktop or easily move it to the server at any time. It doesn’t even matter if the server is running a different operating system, with a JumpBox everything is self contained.

Trip Tracker is a position tracking client-server system. Trip Tracker is designed to assist people in setting up a real-time tracking environment with either a private or public tracking server.
The Trip Tracker GPS client sends coordinates to the tracking server to update its position. In the event that the GPS client loses its Internet connection, it can send all collected coordinates to the tracking server as soon as its back online.
The tracking server saves all the coordinates and can forward them to listening map clients.
Version restrictions:
- The map client can only display a map of Norway, as the WMS server is hardcoded in the server-side PHP script "mapservice.php". This may change in the future. If you know any good WMS servers we might add it to the server-side script, but you still need to add the proper WMS layers in the source code to make it work.
- The GPS client version 0.8 does not set up the Java Communications library properly so it most likely wont find your GPS receiver. We hope to address this issue in the next release quite soon.
- And more...

Link Monitor Applet is a GNOME Panel Applet displaying the round-trip time to one or more hosts in a bar graph.
Main features:
- full ICMP and ICMPv6 support
- configurable scale and delays
- HIG 2.0 compliance

DataGridField is a product which consists of a table input component for Plone.
It uses Javascript to make entering tabular data more user friendly process - there are no round trip HTTP requests to the server when inserting or deleting rows.
Main features:
- Any number of columns set by a developer
- Any number of rows filled by a user
- Insert and deleting rows without submitting a form
- Many different column types

Mirro is an application used to find the closest mirror to your connection.

Mirro will find the closest mirror to your connection, given a file containing addresses. It pings every site extremely quickly, and sorts the reponses based on the number of hops and the round-trip time.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

SAFMQ, one of the first Open Source message queue server, provides high performance message queuing free to the public.
The SAFMQ server provides Asynchronous Messaging. Message Publishers send or enqueue a message with the SAFMQ server.
The SAFMQ server stores that message until the point at which the message can be forwarded on to the client. Message Publishers are assured that the messages are delivered. Thats how SAFMQ got its name.
SAFMQ provides an API to use SAFMQ directly. Simply use the SAFMQ MQBuilder class to specify the location of your SAMFQ server and youre ready to start publishing and subscribing to priority message queues!
Timely Messaging
SAFMQ provides the ability to perform timely message delivery. So, if a Message Publisher wants a message to be read by a Message Subscriber in a certain amount of time, or not read at all, then the Message Publisher can prescribe a Time-To-Live for the message it publishes. SAFMQ will notify the Message Publisher about messages which have outlived their Time-To-Live, or a Message Publisher can choose to ignore the event.
Round-Trip, PsudoSynchronous Messaging
Round-Trip, or PsudoSynchronous Messaging is when a Message Publisher acts as a Message Subscriber after sending a "query" message. A Message Publisher may want to receive information back from the Message Subscriber. Thus after the first message is sent by a Message Publisher and is received by a Message Subscriber, the original Message Publisher and Message Subscriber switch rolls.
SAFMQ provides a special messaging context element for Round-Trip/PsudoSynchronous Messaging. Its called a Receipt ID. When ever a message is Enqueued in a SAFMQ server, it is given a Universally Unique Identifier or UUID for short. When a Round-Trip message event is taking place, the original Message Subscriber publishes a message with a Recipt ID identiacal to the Message ID assigned to the message sent by the original Message Publisher. Then the original Message Publisher (now a subscriber) waits for a message with a Receipt ID equal to the Message ID the original Message Publisher sent.
Batch Processing
Not every task is best handled real-time. Sometime there are real money benefits to send transactions to a trading partner in a large group or batch. SAFMQ can be an intermediary between real-time systems and a back-end batch processor. The real-time system knows that the messages will be delivered, and the batch processor can let data queue up until it is ready to send all the data. The batch system can even respond via SAFMQ and a real-time system can instantly see the results.
Enhancements:
- Additional configuration changes for cross compile to MacOS X

MARC::Crosswalk::DublinCore is a Perl module that can convert data between MARC and Dublin Core.

SYNOPSIS

my $crosswalk = MARC::Crosswalk::DublinCore->new;

# Convert a MARC record to Dublin Core (simple)
my $marc = MARC::Record->new_from_usmarc( $blob );
my $dc = $crosswalk->as_dublincore( $marc );

# Convert simple DC to MARC
$marc = $crosswalk->as_marc( $dc );

# Convert MARC to qualified DC instead
$crosswalk->qualified( 1 );
$dc = $crosswalk->as_dublincore( $marc );

This module provides an implentation of the LOCs spec on how to convert metadata between MARC and Dublin Core format. The spec for converting MARC to Dublin Core is available at: http://www.loc.gov/marc/marc2dc.html, and from DC to MARC: http://www.loc.gov/marc/dccross.html.

NB: The conversion cannot be done in a round-trip manner. i.e. Doing a conversion from MARC to DC, then trying to go back to MARC will not yield the original record.