Free ximian connector software for linux

Ximian-South provides a icon pack for GTK+.

jimmacs and tigerts Ximian-South ported to a Gnome Icon Theme.

Jiplet is short for Java SIP Servlet. Jiplet Container project is an open-source container for server-side SIP applications. An application developer can create a SIP application written in Java using the Jiplet API and deploy the application in the container.
The container provides a number of framework services including support for SIP message parsing and formatting, scoped variables, authentication and authroization, thread-pooling, logging, custom class loading, management interface, etc. It enables application developer to create server-side SIP applications using a component-based model similar to that envisioned by the J2EE architecture.
In fact, it fits very well with the J2EE paradigm for software development and deployment. The jiplet container software can either be run as a standalone Java application or deployed as a service residing in a J2EE server. When running as a J2EE service, the jiplet container can access many of the features offered by the J2EE server.
In addition, The jiplet container is built with the service provider model in mind. In this model, a service provider can host customized SIP applications from their customers in a secure manner similar to the servlet hosting offered by many service providers.
The jiplet container is very similar to a Java HTTP servlet container in concept. A Java HTTP servlet is a Java class that handles HTTP messages from web browsers. Similarly, a jiplet is a Java class that handles SIP messages from SIP user agents (SIP phones and SIP servers).
A servlet container like Apache Tomcat can host one or more web applications (contexts), each consisting of one or more servlets. Similarly, the jiplet container can host one or more SIP applications (contexts) consisting of one or more jiplets.
Similar to the servlet API authored by Sun Microsystems, the jiplet container provides a set of Java classes that jiplet applications extend or use. The services provided by these classes are very similar to those of the servlet API including scoped variables, request forwarding from one jiplet to another, etc.
As in a servlet container, new jiplet applications, or contexts, can be deployed using a zipped file called spr (war is the Java servlet terminology). Since there are differences between the HTTP and SIP protocols, the servlet and the jiplet containers have some notable differences.
However, the jiplet is not a formal specification like the servlet specification. It is also not an implementation of the SIP servlet specification (JSR 116) authored by Sun and its community of users. There are many similarities between the jiplet and the SIP servlet in terms of features. If you are familiar with SIP servlets, you will feel right at home with the jiplet container.
We are planning to continue developing the jiplet container based on feedback provided by that the open-source community. We are hoping that open-source developers will extend this tool and the specification instead of a committee.
Main features:
- Open-source API for developing server-side SIP applications. Based on the JAIN-SIP API.
- Offers component-based development model.
- Servlet-like development and runtime environment.
- Access to powerful JAIN-API from SIP applications.
- JMX management interface for interfacing with management systems.
- Web-based user interface for managing jiplet applications.
- Support for scoped variables including application, session, request, transaction and dialog-scoped variables.
- Support for forwarding SIP messages from one jiplet to another.
- Container-managed authentication and authorization.
- Support for application timers.
- Can run as a standalone application or it can be integrated with JBOSS as a J2EE service.
- Comprehensive support for the service-provider model.
Enhancements:
- The final release (version 1.2) of the NIST SIP stack Reference Implementation has been incorporated into the Jiplet Container and reference applications.
- The new listening point architecture has been integrated into the Jiplet Container SIP connector.
- One connector can now use more than one IP address for SIP messaging.
- Convenience methods have been added to the Jiplet class for jiplet developers to handle additional listening points and SIP providers.
- The Jiplet Container message proxying has been updated to work in a multi-homed environment.
- The software has been tested with Jboss 4.0.5.GA.

Nuxeo Core is an embeddable document management core, based on Nuxeo Runtime. Nuxeo Core provides all necessary low-level services to define, store, manage, audit, request and search content.
It is the kernel of Nuxeo 5 and can also be embedded in third-party applications to provide advanced content management features.
It can run on any Java platform, can be easily extended using plug-ins (thanks to Nuxeo Runtime) and implements JCA (Java EE Connector Architecture) to be easily plugged into existing applications or information systems.
Enhancements:
- This release fixes a bug related to document removal.

Konzept is a small class diagram editor. Major design goal was usability.
The project was inspired by the static structure diagram editor of the Toolkit of Conceptual Modelling. Konzept is a pure Qt application written in Python.
Usage:
- select graphical elements within the toolbox the left
- right mouse button to place graphical shapes
- middle mouse button to connect two shapes with the selected connector type
- double click right mouse button to enjoy the inline editing and intelligent size adjustment
- maybe disable the grid or change its granularity to accomodate your taste
- save your documents somewhere and bring them back by dropping files from your favorite file browser

ruleCore provides a rule engine for event pattern detection.

The ruleCore Engine is an event-driven rule engine that manages and executes reaction rules. The rules are event-condition-action (ECA) style of rules.

The ruleCore Engine provides capabilities for detection of complex patterns of events, called situations. Events can be combined with logical and temporal operators in order to describe complex situations.

When a situation is detected, the ruleCore Engine can execute an action to alert external applications or users of the situation. The ruleCore Engine is fed with events through connectors.

Currently, connector implementations exist for plain sockets, XML-RPC, IBM WebSphere MQ, and TIBCO Rendezvous. Experimental support exists for running the engine within Zope and calling Zope methods when a rule triggers its action.

Evolution Jescs is the Evolution Connector for Sun Java Enterprise System Calendar Server (SJESCS).
This connector supports the WCAP (Web Calendar Access Protocol) 2.0, 3.0, 3.1.
How to setup a JESCS account?
Now it is integrated into "Mail Accounts" under menu "Edit-->Preferences". Click "Add" button to bring up the account setup widzard. In "Identity" page, please input your Full Name and Email Address. In "Receiving Email" page, choose "Sun Calendar WCAP" as the Server Type. Input Host and Username here.
If your server listens to another port instead of the default one (80 for http, 143 for https), please input Host in the "Host:Port" format, such as "calendar.sun.net:8080". For "Use Secure Connection", please choose "Never" for http and "Always" for https.
In "Receiving Options" page, if you want to poll the server for new events and tasks at a different interval than the default 30 minutes, please check the checkbox and choose a interval. Please note that a small interval setting will impact the performance of the connector. If you are sure you are the only one accessing your calendar, you can set the interval to a very large number.
The "Sending Email" page actually is useless for the connector. You can just input anything here so that you can go forward.
In "Account Management" page, please enter your account name here. Then you can finish your JESCS account setting.
Enhancements:
- configure.in: Bump to 2.9.1
- storage/sunone-folder-tree.c: Fix a bug which will cause evolution-jescs to crash when connecting to the calendar server for the first time.

Net::Proxy is a Perl framework for proxying network connections in many ways.

SYNOPSIS

use Net::Proxy;

# proxy connections from localhost:6789 to remotehost:9876
# using standard TCP connections
my $proxy = Net::Proxy->new(
{ in => { type => tcp, port => 6789 },
out => { type => tcp, host => remotehost, port => 9876 },
}
);

# register the proxy object
$proxy->register();

# and you can setup multiple proxies

# and now proxy connections indefinitely
Net::Proxy->mainloop();

A Net::Proxy object represents a proxy that accepts connections and then relays the data transfered between the source and the destination.

The goal of this module is to abstract the different methods used to connect from the proxy to the destination.
A proxy is a program that transfer data across a network boundary between a client and a server. Net::Proxy introduces the concept of "connectors" (implemented as Net::Proxy::Connector subclasses), which abstract the server part (connected to the client) and the client part (connected to the server) of the proxy.

This architecture makes it easy to implement specific techniques to cross a given network boundary, possibly by using a proxy on one side of the network fence, and a reverse-proxy on the other side of the fence.