<?xml version="1.0" encoding="ISO-8859-1" ?>
<rss version="2.0">
 <channel>
  <title>Runtime Hosting</title>
  <link>http://docs.openlinksw.com/virtuoso/runtimehosting.html</link>
  <description>OpenLink Virtuoso Universal Server: Documentation</description>
  <managingEditor>virtuoso.docs@openlinksw.com</managingEditor>
  <pubDate>Wed, 25 Apr 2012 15:27:44 GMT</pubDate>
  <generator>OpenLink Software Documentation Team</generator>
  <webMaster>webmaster@openlinksw.com</webMaster>
  <image>
    <title>OpenLink Virtuoso Universal Server: Documentation</title>
    <url>http://docs.openlinksw.com/virtuoso/../images/misc/logo.jpg</url>
    <link>http://docs.openlinksw.com/virtuoso/runtimehosting.html</link>
    <description>OpenLink Virtuoso Universal Server: Documentation</description>
  </image>
  <item>
    <guid>http://docs.openlinksw.com/virtuoso/rthactivation.html</guid>
    <author>virtuoso.docs@openlinksw.com</author>
    <category>Runtime Environments</category>
    <link>http://docs.openlinksw.com/virtuoso/rthactivation.html</link>
    <pubDate>Wed, 25 Apr 2012 15:27:44 GMT</pubDate>
    <title>Runtime Environments</title>
    <description>The Virtuoso server in its standard build is a single executable.  To
 allow for external customizations based on VSEs the Virtuoso server engine
 becomes a callable library, the main function is re-written to incorporate other
 libraries and a new executable is created.
For example, a Virtuoso server
 that contains PHP support under Windows consists of: 

which replaces the usual 7M virtuoso-odbc-t.exe.
 virtuoso.odbc-php-t.exe is then executed
 in the usual way.

The Linux counterpart would be an
 8M virtuoso-odbc-php-t binary.

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/virtuoso/rthclr.html</guid>
    <author>virtuoso.docs@openlinksw.com</author>
    <category>CLR, .Net &amp; ASPX Host</category>
    <link>http://docs.openlinksw.com/virtuoso/rthclr.html</link>
    <pubDate>Wed, 25 Apr 2012 15:27:44 GMT</pubDate>
    <title>CLR, .Net &amp; ASPX Host</title>
    <description>The Common Language Runtime (CLR) is the foundation upon which the
 Microsoft® .NET strategy is built.  The CLR provides an execution environment
 that manages running code and provides services that make software development
 easier.  These services include automatic memory management, cross-language
 integration, interoperability with existing code and systems, simplified
 deployment, and a fine grained security system.  The .NET platform also
 brings with it a new programming language called C#.  It is very similar to Java
 and allows developers to make full use of all features available on the .NET runtime.

The CLR can run a variety of different types of applications, such as:
 console applications, Web server scripts, traditional Win32-based applications,
  and more.

The CLR provides a language specification for compilers to generate classes
 and code that can interoperate with other programming languages (The
 Common Language Specification: CLS) .  Any API that is written using a
 CLS provider language can be used by any language that is a CLS consumer.
 Compilers generate code in a format called Common Intermediate Language
 (CIL) which is an intermediate representation of a compiled program and is
 easy to compile to native code or be compiled using Just-in-Time (JIT)
 engines.  The restrictions placed by the runtime on the CIL byte codes
 ensures good potential for code optimization by the JIT compiler.  The runtime
 environment provides garbage collection, threading and a comprehensive class
 library.  All these things make code development easier and more appealing
 by allowing a mixture of languages to be collaborating to produce results, all
 contained within a managed sandbox to prevent bugs from breaking other running
 programs.

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/virtuoso/rthclrmono.html</guid>
    <author>virtuoso.docs@openlinksw.com</author>
    <category>CLR &amp; Mono</category>
    <link>http://docs.openlinksw.com/virtuoso/rthclrmono.html</link>
    <pubDate>Wed, 25 Apr 2012 15:27:44 GMT</pubDate>
    <title>CLR &amp; Mono</title>
    <description>The Mono Project is an open development initiative sponsored by Ximian
 that is working to develop an open source, Unix version of the Microsoft .NET
 development and run time platform.  Its objective is to enable Unix developers to build
 and deploy cross-platform .NET Applications.  Likewise, this expands the
 capabilities of Windows programmers, this project opens .NET to non
 Windows platforms.  Mono will implement various Microsoft technologies that
 have now been submitted to the ECMA for standardization.

The Goal is similar to that of Java, implementing a common virtual machine
 on multiple operating systems, however you are not restricted to one
 language.

Like .NET, Mono contains a Common Language Infrastructure (CLI) virtual,
 machine that contains a class loader, Just-in-time compiler, and a garbage
 collecting runtime; a class library that can work with any language which
 works on the CLR; a compiler for the C# language.

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/virtuoso/javaextvm.html</guid>
    <author>virtuoso.docs@openlinksw.com</author>
    <category>Embedded Java VM API</category>
    <link>http://docs.openlinksw.com/virtuoso/javaextvm.html</link>
    <pubDate>Wed, 25 Apr 2012 15:27:44 GMT</pubDate>
    <title>Embedded Java VM API</title>
    <description>The Java VM is an embedded system within Virtuoso that allows the
  calling of class Java methods and getting class properties.  It uses the
  JAVA JNI API to interact with the JAVA VM.

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/virtuoso/cinterface.html</guid>
    <author>virtuoso.docs@openlinksw.com</author>
    <category>Virtuoso Server Extension Interface (VSEI) (C Interface)</category>
    <link>http://docs.openlinksw.com/virtuoso/cinterface.html</link>
    <pubDate>Wed, 25 Apr 2012 15:27:44 GMT</pubDate>
    <title>Virtuoso Server Extension Interface (VSEI) (C Interface)</title>
    <description />
  </item>
  <item>
    <guid>http://docs.openlinksw.com/virtuoso/vseplugins.html</guid>
    <author>virtuoso.docs@openlinksw.com</author>
    <category>VSEI Plugins</category>
    <link>http://docs.openlinksw.com/virtuoso/vseplugins.html</link>
    <pubDate>Wed, 25 Apr 2012 15:27:44 GMT</pubDate>
    <title>VSEI Plugins</title>
    <description>Virtuoso functionality can be enhanced through external libraries by
loading shared objects or DLLs.  The new functions are written in a language of
the developer&#39;s choice and compiled to produce a shared library appropriate to the operating
system.  The path to the shared library must be declared in the Virtuoso INI
file and the server restarted before it can be used.

The Virtuoso INI file uses a [Plugins] configuration section for listing
shared libraries for the server to load upon startup.  The layout is as
follows:

Virtuoso reads the Load1, Load2, ... LoadN lines from the [Plugins]
section and attaches them according to their type. 

</description>
  </item>
 </channel>
</rss>

