RainWorx.FrameWorx.Providers.Listing Namespace

Provides basic listing type functionality that may or may not be overridden in some implementations

The IListing Interface is the base interface for all listing types. It handles the creation and update of listing types. In general, it expects UserInput as input from the web page. Since we would consider *any* logic in the MVC layer misplaced (because MVC is supposed to be presentation, and BLL is supposed to be logic) UserInput is just basic data a user could send, mostly consisting of key/value pairs from a webform. Listing Types are generally a set of fields common to all (or most) listings, and a "property bag" of custom fields for additional logic. This property bag should contain information required for internal logic for the listing type, but generally should not contain queryable data. An example would be for Dutch Auctions where "quantity" is part of the internal logic of a Dutch Auction, but most likely users wouldn't be querying listings based on "quantity"... "Show me all listings where quantity is 5..."

The IListingAction interface is the base interface for all listing actions (bids, purchases, etc...). It handles the creation of Listing Actions for all Listings using a two step process. When initiated by a user during the normal course of business, it first converts the raw UserInput into a ListingAction, and then submits that ListingAction for the remainder of the workflow. When initiated by the Delete/Rollback system by an adminitrator, the ListingAction has already been persisted to the back end data store and so that ListingAction is submitted for the remainder of the workflow.

The IListingOffer interface is the base interface for listing offers. It handles the sending and responding to offers.

The IListingResolver interface is the base interface for the workflow that should take place when a Listing officially ends.