Shi, Thanks for the feedback. So in your case the products would be ad positions, whereas, I was thinking they would be count packages (eg. 1K, 2K, etc). In your case, you would just make the impression count the order quantity listed for that package in the OrderItem record? That sounds like it would work. We could use promotions to put together special packages. Thanks for bringing up the point that people want to buy ad positions - I had not thought of that. I don't have much experience with this. I guess there are other conditions buyers will want to specify - what would they be? Of course, we want to be able to tie ads to the user profile if they are logged in - we should be talking about how those facts will be stored.
Your comments don't deal with how the ad images are tied in, do they? Any thoughts there? I will want the ad content to be rendered on the front end via the screen widget code. It may require some changes in the content management package to go straight to content. My thought is to use the CMS to place images in the file system where they can be accessed directly via the web server or via the CMS. -Al On 12/30/06, Shi Yusen <[EMAIL PROTECTED]> wrote:
Hi Al, I don't know why I can't send this to the list, so I send it to you directly. I think it would be better if the ad positions can be listed as products in a special catalog. A customer can order an ad position and assign the ad type such as image, flash and etc. and from date, thru date. In the frontend, just insert some javascript code as Google did. Is this possible? Shi Yusen/Beijing Langhua Ltd. 在 2006-12-30六的 10:56 -0700，Al Byers写道： > Has there been any work done on an ad rotator service? > > If not, I think I would like to build off of the subscription model. > I would create virtual products with different variants for impression > counts (eg. 1k, 5k, etc) per month (or time period). > I would not link Product to SubscriptionResource via > ProductSubscriptionResource because I want to reuse the same product for > different customers and I can't have static content (ie. ad images) tied to > a product. > > I want to use Subscriptions so that I have a persistent object to tie > Content entities to. I would use the ShoppingList to handle recurring > billing - which generates a new order on each cycle. I want to use the > subscription model because there will be functionality to handle commissions > and billing - but those things are not really tied to Subscription, but it > seems that there would be some common elements. > > So I think I will need a new entity, AdContentHit, that would provide a sort > of de-normalized record for both capturing the ads tied to a user and > managing their delivery. > > AdContentHit > - subscriptionId > - subscriptionSeqId > - contentId > - imageUrl - a quick way to deliver the image, rather than going thru the > contentId. Would need to get modified if the content location changed > - currentQuota - number of impressions scheduled for the month (or time > period) > - currentHits - number of impressions delivered within month or time period > - deliveryRate - i am thinking about indexing this field and using it to > find the next image to deliver. It would be the currentQuota / currentHits > if currentHits is > 0 > or just equal to currentQuota if currentHits > == 0. This formula seems like it would work even if you go over your quota - > which will certainly happen. > Okay, I see where this will not work unless all > currentHits get zeroed out each night and currentQuota is for a 24 hour > period - so that all ads are on the same point > of reference. There is probably a better way to do > this. Have not looked at it much. Hoping for some suggestions. > - fromDate > - thruDate > - totalHits > - imageSize (medallion, banner, etc) > > These are just some initial thoughts. Anyone out there have some knowledge > to share? > > Thanks, > > Al
