<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Delegates And Events</title>
<link rel="stylesheet" type="text/css" href="../../../style.css">
</head>
<body>
<div class="CommonContent">
<div class="CommonContentArea">
<h1>Delegates And Events</h1>
<p><font color="#990000">This topic applies to .NET version only</font> <br></p>
<p><span name="cs_wiki_filter" csw_filters="net"></p>
<p>Db4o rules for delegate fields are very straightforward: <b>delegates are simply not stored.</b><br><br>Events and delegates are generally used for binding user interface elements and domain models together. The Db4o team felt that not storing delegate fields by default was more appropriate than opening what could potentially be a very nasty can of worms (just think of a text box bound to a Customer.Changed event).<br><br>After careful thought we can easily add delegate persistence to our domain model by either installing translators for the delegate types of interest or reconnecting the necessary objects upon activation using callbacks.<br><br>For details see the specific chapters on <a href="../translators.html" class="wikiLink">Translators</a> and <a href="../callbacks.html" class="wikiLink">Callbacks</a>.<br><br></span><br></p></div>
</div>
<div id="footer">
This revision (8) was last Modified 2007-05-07T09:36:25 by Tetyana.
</div>
</body>
</html>
