livedomain Wiki Rss Feed

New Comment on "Model Proxy"

rofr — Mon, 26 Nov 2012 20:41:32 GMT

@Roger, yes, you are correct and this is the required behavior here. We want to intercept and log all incoming method calls. Whatever other internal calls which are triggered will be triggered again when the commands are replayed during system restore.

New Comment on "Model Proxy"

RogerAlsing — Thu, 25 Oct 2012 11:06:27 GMT

As far as I know, real proxy / transparent proxy et al does not support "self interception" , e.g. if one of your commands calls another command, the last invocation will not be intercepted.. is this the case here too?

Updated Wiki: Contributing

rofr — Thu, 25 Oct 2012 09:55:54 GMT

Contributing to LiveDB

So you're interested in developing for #liveDB? Excellent! There are many areas where we could use some help:

Core development tasks

Custom serializers
Custom storage modules
Instrumentation hooks
Custom synchronizers
Logging adapters
Null storage module
Encryption
Compression
Configuration framework
Adding features to transparent proxying
Store utility functions
Visualization

Other stuff

Performance testing/benchmarks
Add more tests
General refactoring
Add continous integration and delivery
Documentation :)
Writing examples and blogging
Running examples on mono
Creating reusable models

How we work

We don't have a backlog or roadmap. We decide on a feature based on demand or inspiration and then just go for it! Here's the process for developing a feature:

Rough overall design of the feature using a notebook, napkin, envelope or whiteboard.
Implement the feature on a dedicated vcs branch
Review and refine the design, goto 2
Merge it into the dev branch

Skills required

Solid OO design skills
MS Test
Visual Studio and Nuget
DVCS with GIT

Setup and workflow

Sign up for a codeplex account
Create a fork
Clone to your workstation
Create a feature (or hotfix) branch to work on
Do your stuff
merge into dev branch (or master for hotfixes) and make sure all tests pass
Create a pull request

Learn more about forks and pull requests with codeplex

Do your stuff!

Keep your code changes small and focused. Small commits are preferred!
Write tests!
Write proper commit messages! Commit messages should be helpful to others.
Do your work in the open. Share your ideas with the community as early as possible.

System requirements

Visual Studio 2010
Visual Studio built in tests
Nuget Package manager with package restore enabled
Git client

Updated Wiki: Contributing

rofr — Thu, 25 Oct 2012 09:15:35 GMT

Contributing to LiveDB

So you're interested in developing for #liveDB? Excellent! There are many areas where we could use some help:

Core development tasks

Custom serializers
Custom storage modules
Instrumentation hooks
Custom synchronizers
Logging adapters
Null storage module
Encryption
Compression
Configuration framework
Adding features to transparent proxying
Store utility functions
Visualization

Other stuff

Performance testing/benchmarks
Add more tests
General refactoring
Add continous integration and delivery
Documentation :)
Writing examples and blogging
Running examples on mono
Creating reusable models

How we work

We don't have a backlog or roadmap. We decide on feature based on demand and then just go for it! Here's the process for developing a feature:

We do a rough overall design of the feature using a notebook, napkin, envelope or whiteboard.
Implement the feature on a dedicated vcs branch
Review and refine the design, goto 2
Merge it into the dev branch

Skills required

Solid OO design skills
MS Test
Visual Studio and Nuget
DVCS with GIT

Setup and workflow

Sign up for a codeplex account
Create a fork
Clone to your workstation
Create a feature (or hotfix) branch to work on
Do your stuff
merge into dev branch (or master for hotfixes) and make sure all tests pass
Create a pull request

Do your stuff!

Keep your code changes small and focused. Small commits are preferred!
Write tests!
Write proper commit messages! Commit messages should be helpful to others.
Do your work in the open. Share your ideas with the community as early as possible.

System requirements

Visual Studio 2010
Visual Studio built in tests
Nuget Package manager with package restore enabled
Git client

Updated Wiki: Contributing

rofr — Thu, 25 Oct 2012 09:13:46 GMT

Contributing to LiveDB

So you're interested in developing for #liveDB? Excellent! There are many areas where we could use some help:

Core development tasks

Custom serializers
Custom storage modules
Instrumentation hooks
Custom synchronizers
Logging adapters
Null storage module
Encryption
Compression
Configuration framework
Adding features to transparent proxying
Store utility functions
Visualization

Other stuff

Performance testing/benchmarks
Add more tests
General refactoring
Add continous integration and delivery
Documentation :)
Writing examples and blogging
Running examples on mono
Creating reusable models

How we work

We don't have a backlog or roadmap. We decide on feature based on demand and then just go for it! Here's the process for developing a feature:

We do a rough overall design of the feature using a notebook, napkin, envelope or whiteboard.
Implement the feature on a dedicated vcs branch
Review and refine the design, goto 2
Merge it into the dev branch

Skills required

Solid OO design skills
MS Test
Visual Studio and Nuget
DVCS with GIT

Setup and workflow

Sign up for a codeplex account
Create a fork
Clone to your workstation
Create a feature (or hotfix) branch to work on
Do your stuff
merge into dev branch (or master for hotfixes) and make sure all tests pass
Create a pull request

fish

Do your stuff!

Keep your code changes small and focused. Small commits are preferred!
Write tests!
Write proper commit messages! Commit messages should be helpful to others.
Do your work in the open. Share your ideas with the community as early as possible.

System requirements

Visual Studio 2010
Visual Studio built in tests
Nuget Package manager with package restore enabled
Git client

Updated Wiki: Contributing

rofr — Thu, 25 Oct 2012 09:12:45 GMT

Contributing to LiveDB

So you're interested in developing for #liveDB? Excellent! There are many areas where we could use some help:

Core development tasks

Custom serializers
Custom storage modules
Instrumentation hooks
Custom synchronizers
Logging adapters
Null storage module
Encryption
Compression
Configuration framework
Adding features to transparent proxying
Store utility functions
Visualization

Other stuff

Performance testing/benchmarks
Add more tests
General refactoring
Add continous integration and delivery
Documentation :)
Writing examples and blogging
Running examples on mono
Creating reusable models

How we work

We don't have a backlog or roadmap. We decide on feature based on demand and then just go for it! Here's the process for developing a feature:

We do a rough overall design of the feature using a notebook, napkin, envelope or whiteboard.
Implement the feature on a dedicated vcs branch
Review and refine the design, goto 2
Merge it into the dev branch

Skills required

Solid OO design skills
MS Test
Visual Studio and Nuget
DVCS with GIT

Setup and workflow

Sign up for a codeplex account
Create a fork
Clone to your workstation
Create a feature (or hotfix) branch to work on
Do your stuff
merge into dev branch (or master for hotfixes) and make sure all tests pass
Create a pull request

fish

Do your stuff!

Keep your code changes small and focused. Small commits are preferred!
Write tests!
Write proper commit messages! Commit messages should be helpful to others.
Do your work in the open. Share your ideas with the community as early as possible.

System requirements

Visual Studio 2010
Visual Studio built in tests
Nuget Package manager with package restore enabled
Git client

Updated Wiki: Contributing

rofr — Thu, 25 Oct 2012 09:10:47 GMT

Contributing to LiveDB

So you're interested in developing for #liveDB? Excellent! There are many areas where we could use some help:

Core development tasks

Custom serializers
Custom storage modules
Instrumentation hooks
Custom synchronizers
Logging adapters
Null storage module
Encryption
Compression
Configuration framework
Adding features to transparent proxying
Store utility functions
Visualization

Other stuff

Performance testing/benchmarks
Add more tests
General refactoring
Add continous integration and delivery
Documentation :)
Writing examples and blogging
Running examples on mono
Creating reusable models

How we work

We don't have a backlog or roadmap. We decide on feature based on demand and then just go for it! Here's the process for developing a feature:

We do a rough overall design of the feature using a notebook, napkin, envelope or whiteboard.
Implement the feature on a dedicated vcs branch
Review and refine the design, goto 2
Merge it into the dev branch

We are f
http://nvie.com/posts/a-successful-git-branching-model/

Skills required

Solid OO design skills
MS Test
Visual Studio and Nuget
DVCS with GIT

Setup and workflow

Sign up for a codeplex account
Create a fork
Clone to your workstation
Create a feature (or hotfix) branch to work on
Do your stuff
merge into dev branch (or master for hotfixes) and make sure all tests pass
Create a pull request

Do your stuff!

Keep your code changes small and focused. Small commits are preferred!
Write tests!
Write proper commit messages! Commit messages should be helpful to others.
Do your work in the open. Share your ideas with the community as early as possible.

System requirements

Visual Studio 2010
Visual Studio built in tests
Nuget Package manager with package restore enabled
Git client

Updated Wiki: Contributing

rofr — Thu, 25 Oct 2012 07:22:29 GMT

Contribute to LiveDB

Setting up

Fork the project

Fork the project and add an upstream for
You can find https://help.github.com/articles/fork-a-repo on github's help pages.

Updated Wiki: Home

rofr — Wed, 24 Oct 2012 11:26:40 GMT

#liveDB - build faster systems faster

Accessing data from RAM is orders of magnitude faster than reading from disk. Also, data in RAM can be in a native format eliminating the need for object/relational mapping or other translation, significantly reducing developer time and cost.

Project Description

liveDB is an in-memory database engine for Microsoft .NET providing full ACID support, lightning fast performance and offering a significant reduction of development and operational costs. liveDB is built on Live Domain Technology, a custom implementation of the Prevalent System Architecture.

Release Notes - 0.8.0-preview
Contributing
Documentation (on this site)

Real world systems running LiveDB

Updated Wiki: Child Models

rofr — Mon, 22 Oct 2012 15:14:53 GMT

Child Models

Note! This is a highly experimental feature and needs more testing!
This is a feature which enables reuse of existing models by including them in your Model. Here's a part of the Model class supporting this feature:

public class Model
{
   //keyed by model type
   private Dictionary<Type,Model> _childModels;

   public T ChildFor<T>() where T : Model
   {
      //return a model of type T, creating one if necessary
   }
}

And here's an example model (partial) which could be a good candidate for reuse:

[Serializable]
public class UsersModel : Model
{
   public void Register(string name, string passwordHash)
   {
      ...
   }
   public bool Authenticate(string user, string password)
   {
      ...
   }
}

Including and accessing the UserModel using a transparent proxy:


//get a proxy for the main model
var db = Db.For<MyModel>();

//Get a child proxy and do stuff 
UsersModel userDb = db.ChildFor<UsersModel>()
string hash = CryptoHelper.HashFor("DOHnuts");
userDb.Register("homer", hash);
bool isAuthenticated = userDb.Authenticate("homer", "DOHnuts");

Or using traditional command/query style.

[Serializable]
public class RegisterUserCommand : Command<UsersModel>
{
   //note how this command targets UsersModel
}

IEngine<MyModel> engine = Engine.For<MyModel>();

//Execute() now accept commands targeted for any model type and routes to child model
engine.Execute(new RegisterUserCommand("homer", hash));

Updated Wiki: Documentation

rofr — Mon, 22 Oct 2012 15:13:07 GMT

Documentation

Quick Start Guide
FAQ
Modeling
- Child Models
- Writing Commands
- Writing Queries
  - Compiled Linq Queries
- Views
- Schema evolution
Engine
Client API
Configuration
- Extensibility
- File storage (default)
- Sql storage
Snapshots
Store Utility - journal and snapshot conversion tool

Updated Wiki: file upload test

rofr — Mon, 22 Oct 2012 15:00:20 GMT

ooioij
Koala.jpg

Updated Wiki: file upload test

rofr — Mon, 22 Oct 2012 14:59:44 GMT

ooioij
download warez

Updated Wiki: file upload test

rofr — Mon, 22 Oct 2012 14:58:59 GMT

ooioij

Updated Wiki: file upload test

rofr — Mon, 22 Oct 2012 14:57:40 GMT

ooioij

Updated Wiki: Child Models

rofr — Mon, 22 Oct 2012 14:57:23 GMT

Child Models

public class Model
{
   //keyed by model type
   private Dictionary<Type,Model> _childModels;

   public T ChildFor<T>() where T : Model
   {
      //return a model of type T, creating one if necessary
   }
}

And here's an example model (partial) which could be a good candidate for reuse:

[Serializable]
public class UsersModel : Model
{
   public void Register(string name, string passwordHash)
   {
      ...
   }
   public bool Authenticate(string user, string password)
   {
      ...
   }
}

Including and accessing the UserModel using a transparent proxy:


//get a proxy for the main model
var db = Db.For<MyModel>();

//Get a child proxy and do stuff 
UsersModel userDb = db.ChildFor<UsersModel>()
string hash = CryptoHelper.HashFor("DOHnuts");
userDb.Register("homer", hash);
bool isAuthenticated = userDb.Authenticate("homer", "DOHnuts");

Or using traditional command/query style.

[Serializable]
public class RegisterUserCommand : Command<UsersModel>
{
   //note how this command targets UsersModel
}

var engine = Engine.For<MyModel>();
//handlers now accept commands targeted for any model type
engine.Execute(new RegisterUserCommand("homer", hash));

Updated Wiki: Child Models

rofr — Mon, 22 Oct 2012 14:42:30 GMT

Child Models

This is a feature which enables reuse of existing models by including them in your Model. Here's a part of the Model class supporting this feature:

public class Model
{
   //keyed by model type
   private Dictionary<Type,Model> _childModels;

   public T ChildFor<T>() where T : Model
   {
      //return a model of type T, creating one if necessary
   }
}

And here's an example model (partial) which could be a good candidate for reuse:

[Serializable]
public class UsersModel : Model
{
   public void Register(string name, string passwordHash)
   {
      ...
   }
   public bool Authenticate(string user, string password)
   {
      ...
   }
}

Including and accessing the UserModel using a transparent proxy:


//get a proxy for the main model
var db = Db.For<MyModel>();

//Get a child proxy and do stuff 
UsersModel userDb = db.ChildFor<UsersModel>()
string hash = CryptoHelper.HashFor("DOHnuts");
userDb.Register("homer", hash);
bool isAuthenticated = userDb.Authenticate("homer", "DOHnuts");

Updated Wiki: Child Models

rofr — Mon, 22 Oct 2012 14:30:55 GMT

Child Models

This is a feature which enables reuse of existing models by including them in your Model. Here's the parts of th Model class supporting this feature:


public class Model
{
   //keyed by model type
   private Dictionary<Type,Model> _childModels;

   public T ChildFor<T>() where T : Model
   {
      //return a model of type T, creating one if necessary
   }
}

And here's an example model (partial) which could be a good candidate for reuse:

[Serializable]
public class UsersModel : Model
{
   public void Register(string name, string passwordHash)
   {
      ...
   }
   public bool Authenticate(string user, string password)
   {
      ...
   }
}

Updated Wiki: Child Models

rofr — Mon, 22 Oct 2012 14:29:04 GMT

Child Models

This is a feature which enables reuse of existing models by including them in your Model. Here's the parts of th Model class supporting this feature:

code:c
public class Model
{
//keyed by model type
private Dictionary<Type,Model> _childModels;

public T ChildFor<T>() where T : Model
{
//return a model of type T, creating one if necessary
}
}
code:c
And here's an example model (partial) which could be a good candidate for reuse:

{code:c#}
Serializable
public class UsersModel : Model
{
public void Register(string name, string passwordHash)
{
...
}
public bool Authenticate(string user, string password)
{
...
}
}
{code:c#}

Updated Wiki: Child Models

rofr — Mon, 22 Oct 2012 14:28:19 GMT

Child Models

This is a feature which enables reuse of existing models by including them in your Model. Here's the parts of th Model class supporting this feature:

{code:c#}
public class Model
{
//keyed by model type
private Dictionary<Type,Model> _childModels;

public T ChildFor<T>() where T : Model
{
//return a model of type T, creating one if necessary
}
}
{code:c#}
And here's an example model (partial) which could be a good candidate for reuse:

{code:c#}
Serializable
public class UsersModel : Model
{
public void Register(string name, string passwordHash)
{
...
}
public bool Authenticate(string user, string password)
{
...
}
}
{code:c#}

livedomain Wiki Rss Feed

New Comment on "Model Proxy"

New Comment on "Model Proxy"

Updated Wiki: Contributing

Contributing to LiveDB

Core development tasks

Other stuff

How we work

Skills required

Setup and workflow

Do your stuff!

System requirements

Updated Wiki: Contributing

Contributing to LiveDB

Core development tasks

Other stuff

How we work

Skills required

Setup and workflow

Do your stuff!

System requirements

Updated Wiki: Contributing

Contributing to LiveDB

Core development tasks

Other stuff

How we work

Skills required

Setup and workflow

Do your stuff!

System requirements

Updated Wiki: Contributing

Contributing to LiveDB

Core development tasks

Other stuff

How we work

Skills required

Setup and workflow

Do your stuff!

System requirements

Updated Wiki: Contributing

Contributing to LiveDB

Core development tasks

Other stuff

How we work

Skills required

Setup and workflow

Do your stuff!

System requirements

Updated Wiki: Contributing

Contribute to LiveDB

Setting up

Updated Wiki: Home

#liveDB - build faster systems faster

Project Description

Other Links

Real world systems running LiveDB

Updated Wiki: Child Models

Child Models

Updated Wiki: Documentation

Documentation

Updated Wiki: file upload test

Updated Wiki: file upload test

Updated Wiki: file upload test

Updated Wiki: file upload test

Updated Wiki: Child Models

Child Models

Updated Wiki: Child Models

Child Models

Updated Wiki: Child Models

Child Models

Updated Wiki: Child Models

Child Models

Updated Wiki: Child Models

Child Models