tags:

views:

2

answers:

0

I want to have an e-card feature for my B2B clients, but need help on implementing. Basically a user will be able to come to our site, click on the e-card link. When an ability to select front design and inside pattern will be able, after when user will have to enter recipients info (name, surname and email), select a background song from our list, and lastly he will have to enter his 170 characters message. After user press send a flash mini clip (an e-card) will be generated on our server. This card will stay on our server as long the user will want because he will be able to view his “SENT” cards and the cards he have received. How everything should be handled in the database and in the backend? I have thought of:

ECards

CardID FrontDesign InsideDesign RecipientsName RecipientsSurname RecipientsEmail Song Message(170 chrcts)

Ecards Received

CardID From To Date Action (view/reply/delete)

Ecards Sent

CardID To From Date Action (view/resent/delete)

Would you do the same approach? Also, Storing 170 characters messages in the database is not very wise I suppose? Also, how to handle this Ecards sent feature when a registered user sents a message to not a site user?

Thank you for you help.