You are here: Platform Specific Issues > Web Environment

Web Environment

db4o runs perfectly well in a web environment. It can be used to build your web-application.

In most web-application multiple concurrent requests are processes. Normally you want to isolate each request from another. You can use db4o transactions to archive this isolation. See "Isolation in Web-Applications"

In most web-applications a object is only alive during a request. So you have to identify objects across requests. Therefore you need to add an additional id to your object. There are different possibilities for this. See "Disconnected Objects"

When you run in a web-environment, you often have stricter security limitations. Take a look at the security requirements. See "ASP.NET Security"

Take a look how you create a object-container for each request. See "ASP.NET Request Example"

You might run into trouble because of ASP.NET assembly naming policy. See "ASP.NET Assembly Naming"

Take a look a small example ASP.NET MVC application, which includes all these concerns. See "ASP.NET MVC Example"

More Information

Additional information about using db4o in ASP.NET environment can be found in db4o Project Spaces. The following community projects featuring db4o ASP.NET membership providers exist: