Sophie

Sophie

distrib > Fedora > 15 > i386 > by-pkgid > 864d1c3c3cd8df4e3a2692faf8776e05 > files > 1077

db4o-doc-7.4-2.fc13.i686.rpm

<html>
  <head>
    <META http-equiv="Content-Type" content="text/html; charset=utf-8">
    <title>Cross-Platform Applications</title>
    <link rel="stylesheet" type="text/css" href="../../style.css">
  </head>
  <body>
    <div class="CommonContent">
      <div class="CommonContentArea">
        <h1>Cross-Platform Applications</h1><p>db4o is a native java and .NET database.&amp;nbsp; It reads Java and .NET objects and stores
them in a platform independent format. In the runtime the database data is
reconstructed into class objects using reflection. However, as the database
storage is actually platform-independent, it does not matter if the data will
be reconstructed into a java or .NET class object as soon as the class
definition matches. Thus the same db4o database can be used both with Java and
.NET application.

&nbsp;</p><p>Further Reading:</p><ul><li><a href="cross-platform_applications/configuration.html" class="wikiLink">Configuration</a></li><li><a href="../implementation_strategies/aliases/cross-platform_aliasing.html" class="wikiLink">Using Aliasing for Cross-Platform Development</a></li><li><a href="cross-platform_applications/limitations_of_db4o_cross-platform_usage.html" class="wikiLink">Limitations Of Db4o Cross-Platform Usage</a><br></li></ul></div>
    </div>
    <div id="footer">
					This revision (5) was last Modified 2007-09-02T13:42:56 by Tetyana.
				</div>
  </body>
</html>