Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Backgrounders

Persisting objects in tables

ASP.NET for people who did not bother until now

What uigen.exe does
uigen.exe is a program generator. It uses templates to derive a basic web application from the domain model. This article explains how this works in detail. You can write your own templates for new types of web applications.

re-strict dictionary and overview
restrict is re-motion's security module. Not much documentation exists at this time, but the article gives you an impression of how re-strict works.

On re-bind's data source controls
re-motion brings its own set of smart web controls. These controls bind to custom data source controls. This article explains the capabilities of various types of re-motion's (re-bind's) data source controls.

Objects in perma-URLs
Per default, re-motion works with Server.Transfer, what precludes unique URLs for each domain object instance. This article explains how to program for "perma-URLs", i.e. unique URLs for each domain object instance.

Hints on how to implement pessimistic locking for re-store
re-store locks domain objects optimistically, i.e. the users who writes back modifications first have their changes committed to the database. This is in contrast to MS Word: in MS Word, the users who open the document first have permission to write back modifications (= pessimistic locking). This article explains how to implement pessimistic locking for (all or just some) classes of domain objects.

Working with XML queries and the query manager

Junction objects
re-store supports 1:1 relations and 1:n relations. This article explains how to implement m:n relations using junction objects.

How to implement pessimistic locking in re-store

Globalization remarks
Everything you ever wanted to know about globalization in re-motion – and more!

Enlisting domain objects (deprecated)
Having the same domain object in two root transactions is a bad idea and not possible by default. This article explains how to enlist domain objects in more than one transaction.

  • No labels