﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Document based modeling: Auctions</title><description>Bil,
I would probably use separate Auctions for each of those items / price points</description><link>http://ayende.com/84993/document-based-modeling-auctions#comment5</link><guid>http://ayende.com/84993/document-based-modeling-auctions#comment5</guid><pubDate>Thu, 15 Sep 2011 03:41:21 GMT</pubDate></item><item><title>Bil Simser commented on Document based modeling: Auctions</title><description>Hmmm... I have a similar model for a silent auction solution I built internally however how would you suggest an alteration to handle individual items. Quantities are fine for bulk purchases where all items are the same, but what about tracking bids on each item and each item in the bulk collection having it's own attributes.

Two examples. First I have 15 Flying Monkey Dolls. So I need to handle bids separately on all 15 of them because not everyone is going to pay the same price. (I think you might handle this in your bids post).

The other example is 15 individual prices for each item (from the auction side, not the bid). So I have 15 Flying Monkey Dolls in stock that I want to put up for auction but I want to set the price for 5 of them at $10, 5 of them at $15, and 5 of them at $20 (maybe I'm conducting a social experiment to see if people flock to the lowest priced item first).

Does this change the model(s) at all?</description><link>http://ayende.com/84993/document-based-modeling-auctions#comment4</link><guid>http://ayende.com/84993/document-based-modeling-auctions#comment4</guid><pubDate>Tue, 13 Sep 2011 14:02:49 GMT</pubDate></item><item><title>Ayende Rahien commented on Document based modeling: Auctions</title><description>Winston,
That is exactly what we are doing in the first alternative.</description><link>http://ayende.com/84993/document-based-modeling-auctions#comment3</link><guid>http://ayende.com/84993/document-based-modeling-auctions#comment3</guid><pubDate>Wed, 07 Sep 2011 08:22:57 GMT</pubDate></item><item><title>Scooletz commented on Document based modeling: Auctions</title><description>Now we are talking! You did not mark your soultion with so popular these days DDD tag, nonetheless it's very close to the _aggregating_ and storing references to entities. Nice showing the way, of solving one of the most common scenarios with references to the historical versions of entities. I find the versioning bundle great addition to the pool of possible solutions.</description><link>http://ayende.com/84993/document-based-modeling-auctions#comment2</link><guid>http://ayende.com/84993/document-based-modeling-auctions#comment2</guid><pubDate>Wed, 07 Sep 2011 05:33:48 GMT</pubDate></item><item><title>Winston Junior commented on Document based modeling: Auctions</title><description>Hi Ayende, if the auction cannot be changed after it's begining, for the sake of simplicity wouldn't be better to maintain the product inside the auction? In this case I'm talking only about performance.
I don't think about a product maintenance because normaly in this kind of site they don't care about the products, the client (user) manage this and normally loss the information about the "version" of the products.

(I know that the code will ensure that a referenced product can't be deleted or that every change will create a new version of the product or something like that)</description><link>http://ayende.com/84993/document-based-modeling-auctions#comment1</link><guid>http://ayende.com/84993/document-based-modeling-auctions#comment1</guid><pubDate>Tue, 06 Sep 2011 16:31:40 GMT</pubDate></item></channel></rss>