Pretty URLs, Separation of Layers and O/R Mapping in Web Forms ASP.NET 2.0

using System;
using System.Collections.Generic;
using System.Collections.Specialized;
using NHibernate.MapClasses;
using NHibernate;

namespace MVC.Controllers
{
    /// <summary>
    /// This is the interface the View will use to communicate 
    /// with the Controller object using a simple Call Back Pattern.
    /// 
    /// Yes - it's the same interface with different names as IDataModel
    /// but this is just a very simple example.  What's important, example
    /// wise, is that this shows how to very loosely connect the view
    /// to the model using interfaces and factories.  This makes for an
    /// extremely flexible architecture that's a breeze to change with
    /// minimal impact to the rest of your code.
    /// </summary>
    public interface IStoreController
    {

        //general 
        MVC.Views.IGeneralView View //has to be object bc. you have many controllers and we use reflections
        {
            get;
            set;
        }

        IList<Product> ListOfBooksForSale();
        IList<CartMember> ListOfCartMembers();
       

        void add_item_to_cart(int id);
        void CreateOrder(IOrderedDictionary InputParameters,ref List<CartMember> CartSession);
        void EmptyCart();
        Order SingleOrder();
      

    }
}