Free connector software for linux

MySQL Connector/ODBC project is an ODBC driver for the MySQL database server.
MySQL is a multithreaded, multi-user SQL database management system (DBMS) which has, according to MySQL AB, more than 10 million installations.
MySQL is owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, which holds the copyright to most of the codebase.
This is similar to the JBoss model and how the Free Software Foundation handles copyright in its projects, and dissimilar to how the Apache project does it, where the software is developed by a public community and the copyright to the codebase is owned by its individual authors.
Enhancements:
- This release fixes a regression in the handling of character data from the server when the server misidentifies it as binary data. (The driver contains a workaround for this server bug that was inadvertantly removed.)

Channel is a generic/simple facility with the purpose of making event dispatching and message passing as straightforward to use as data structures:
Channel is a template library, with its major components configurable as template parameters:
template
<
class Id_Type,
class Id_Trait = IdTrait ,
class SynchPolicy = ACE_MT_SYNCH,
class AllocPolicy,
class Router = MapRouter
>
class Channel
By replacing Id_Type, Id_Trait and Router with various concrete classes, Channel can support table/linear message routing, hierarchical routing and associative routing (Linda style) at the demand of user. The same way, we can use integer, string, POD structs or any class as message ids (provided that proper operations are defined with Id_Trait)
Channel provides complete publish/subscribe interface for channel members (peer threads in message passing and objects in event dispatching) to pub/sub message/event ids/types and send/receive messages/events
Channels are process local entities which can be "connected" to allow transparent distributed communication between members in different channels (Connectors based on tcp socket and unix domain socket are provided as samples)
Namespace control:
The ids published/subscribed by channel members constitute channels namespace.
Channel provides publish/subscribe scope control; When ids are published/subscribed, peers can specify desired scope (LOCAL, REMOTE, GLOBAL)
When 2 channels are connected, their namespaces are automatically "merged", which is transparent to both channel members and programmers. Members can communicate with members in remote channels the same way as with local members (by pub/sub ids).
Namespace merge/integration is controlled by:
Id scope specification
filters and translators defined at channel connections
Channel communication are peer-2-peer; there are no central daemons required for message passing.
Channel support both asynchronous message passing and synchronous event dispatching models.
Channel is built on top of
ACE (Adaptive Communication Environment) to gain platform independence.
Enhancements:
- The framework was ported to Windows XP with VC8.
- Dispatching policy was added as a Channel template parameter to support various dispatching algorithms.
- Broadcast and simple RoundRobin dispatching policies were implemented for testing.
- Callback was changed to functor style so that normal functions and functors can be directly used as callbacks.

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.

Cafeterra provides a message queue-based EAI tool.
Cafeterra is a message queue-based EAI project with a Web user interface for designing, processing, and monitoring inter-application data flows.
Supported connectors are based on an RDBMS, flat files (CSV, fixed length record, XML, HL7, HTML, etc.), LDAP, and SOAP, with others planned.
The main features are message tracking and archival, joining different connectors, an internal scheduler, and raising the flow on events.
Enhancements:
- Support of POP3 and IMAP
- Support of Perl Language in addition to SQL Language for Getmsg, SendMsg, SendMsgBis, AckMsg and GlobalAck
- Evaluate Perl script during design to see if there is any syntax error
- cgi/CafImport.pm : Sort objects; config filename extension handling; remove trailing r
- cgi/Context.pm : handle correctly copying procedure
- cgi/LContainer.pm : remove some trace
- cgi/MFlow.pm : more launch options;
- cgi/Scripts.pm : validate perl scripts (eval)
- cgi/Users.pm : bug when updating user the object attributes were not upadted
- cgi/EN/translate.pm : added some translation
- cgi/FR/translate.pm : idem
- connectors/cafProto.pm : die on open file failure
- connectors/cafpSMTP.pm : bug on attachment; replay_to and fake_to attributes default values
- connectors/refQry.pm : update of datatypeid
- install/Pg/InitSqlScript.pm : Added new protocols/drivers/datatypes/attributes (Mail/POP3/IMAP)
- install/Pg/conf.pm.tpl : Version changed
- install/Pg/d_attrdef.sql : New attributes for new protocols/drivers (Mail/POP3/IMAP)
- install/Pg/d_datatype.sql : New datatypes for new drivers (POP3/IMAP)
- install/Pg/d_driver.sql : New drivers (POP3/IMAP)
- install/Pg/d_protocol.sql : New protocol (Mail)
- install/Pg/index.pl.tpl : Invalidate last value of _currsubmenu
- mains/FlowRt.pm : infinite loop for backtraking when readind dependant messages; avoid die on startsession failure
- mains/FlowTls.pm : classVars misspelling; a query can be an perl script or a sql script
- mains/SFlowRt.pm : handling perl script and sql scripts for getmsg, sendmsg, etc ... in addition to sql script; handle correctly the delins method; LogRbsMessagr enhancement
- mains/SOAPHTTPWS.pm : removed some trace text
- mains/launch.pl : more launch options
- site/help/pageshelp.pm : image reference bug
- site/help/* : translation and orthograph
- site/models/mflowl.html : launch options
- tools/cafUtils.pm : parse mime date
- tools/mydiff.sh : new directories
- DBD/CafeterraDBD.pm : creation
- connectors/cafdPOP3.pm : creation
- connectors/cafdIMAP.pm : creation

podLoader allows you to load content from the Web or other desktop files onto your iPod. Later, for example while traveling, you can check out news from any RSS feed, the weather, or the contents of any file from your desktop.
This application uses the "Notes" feature on third-generation or later touch wheel iPods.
Usage:
In Brief:
- Run podLoadr by double-clicking on podloadr.jar after installing the JRE (or run java -jar podloadr.jar from a command prompt)
- Drag & drop files or links onto the "Files & Links" tab. Browsing or manually typing the file name also works.
- Check some news feeds, add weather zip codes and create a notes on their respective tabs.
- Click the run button (ensure that the iPod is connected and enabled in disk mode).
In Detail:
- In order to load a web page or news feed simply do the following:
- Ensure that your iPod is enabled for disk use. To do this in iTunes:
- Select your iPod under Devices in the Source list.
- Click the Summary tab.
- In the Options section of the Summary pane, click the "Enable disk use" checkbox.
- Note that if the "Manually manage songs and playlists" option is enabled, "Enable disk use" is always enabled or turned on.
- Connect your iPod to your computer as you usually do.
- Exit iTunes - just to be safe.
- Ensure that you have a recent version of the Java runtime (either JDK or JRE) from Sun.
- Run podLoadr by double clicking on podLoadr.jar. Alternatively you can open a command prompt and type java -jar podLoadr.jar
- Note that podLoadr.jar itself can be stored on the ipod and run directly from there. Keep podLoadr.jar and podLoadr.ini together.
- Populate the various tabs in podLoadr.
- Add your custom items to the "Files & Links" tab. This can be done in any of the following ways.
- Drag a file from your desktop or Explorer onto the list
- Drag a link from Internet Explorer or Firefox onto the list (by grabbing the icon in the address box)
- Type the full name of a file in the Name box and click on add
- Click on "Add/Browse" and navigate to the file you need and add it to the list.
- Check off the news feeds that you want from the categorized list.
- Enter the ZIP codes of the weather you want separated by commas.
- Double check the ipod tab to ensure that the drive letter is correct. Or if you have multiple iPods then you can change this setting. (If thats too confusing feel free to send the other iPod my way :-)
To view the note, disconnect your iPod, scroll the menu to Extras, and select Notes. Choose the name the file you created and press the Center button to display the content of the file. You can.t edit the file using iPod, but you can delete it or update it whenever your iPod is connected to your computer.
podLoader uses the "Notes" feature of the iPod to support downloading and offline viewing of online content. Such presentations can be used, for example, as directed lessons or self-paced electronic guided tours. Notes is available on iPod models beginning with third-generation iPod (dock connector) models with the touch wheel.

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.

Evolution Exchange 2.27.3 is professionally designed as the Ximian Connector for Microsoft Exchange, which adds support for Microsoft Exchange 2000 and 2003 to Evolution. Evolution provides integrated mail, addressbook and calendaring functionality to users of the GNOME desktop.

Mergence is a high performance, open source HL7integration engine and application platform. It was developed to fill the need for an open source, fully transactional healthcare integration system capable of handling millions of messages per day, and thousands of concurrent LLP connections. Mergence is based on Apache ServiceMix, a lightweight enterprise service bus which conforms to the JBI standard, and HAPI, an excellent opensource HL7v2 API. We plan to support HL7v3 in the next release.
Mergence is still in heavy development, and documentation is still lacking, but the current release is already production-ready if you dont mind working with some XML. We have a well-tested and solid core in place, which is fully usable. Development of an AJAX administration console is underway and is the main focus of the 2.0 release.
We hope to have more complete documentation available in the next week.
Main features:
- Fully open source, under the GNU General Public License
- Built on standards-based technologies.
- End-to-end persistence with global transactions so no message can ever be lost.
- High-throughput, asynchronous architecture.
- Message vault with encrypted storage (embedded or external DB).
- Flexible message routing and transformation.
- Scriptable using Groovy
- Extensive logging, monitoring, and alerting system.
- Supports active clustering.
- Many bundled connectors, and compatible with any ServiceMix JBI component.
- NIO TCP connectors which can support thousands of concurrent connections.
- Support for processing/transforming flat files of unlimited size.
- Hot deployment of new components and configurations.
- JBI extensions for easily developing new HL7 components.