Almost all paid web services have the concept of Plan. I'd like to model such subsystem so that it can be reused in an OO fashion.
First things first, what's a plan? A plan is a set of capabilities and constrains: E.g. for an online photo album, Plan A can upload a max of 10MB (constrain) and no editing tool (capability), while Plan B can upload a max of 5GB (constrain) and has fancy flex-based editing tool (capability). Each user has a plan, and/or sometimes, each service they subscribe to has a plan. The model and the controller will need some API to talk to this Plan subsystem to determine whether to allow and show the capability (e.g. editing tool), and be able to enforce a constrain. Here's a wall I bump into. How can I make model work with or without the plan (capability and constrain check)? How would you model it? Will the Proxy pattern help? Thanks, Henry Ho http://henrylearnstorock.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
