Hi Robert,
On the server side you can design your data model as a relational database. In your case, the flat tables would be:
Group:
groupId,
groupName
Product:
productId,
groupId,
productName,
imageURL,
price
Model:
modelId,
productId,
color
This is a similar structure to the VO, but isn't limited to one VO definition. You can construct and deconstruct the VO's sent and received from the application with either SQL queries, stored procedures, CFC's, or whatever method your server side technolgy uses. This is just one approach; java-based back-ends can be a little more integrated. But, by keeping the server-side data in relational tables, you add a little more flexibility for future needs.
-TH
--- In [email protected], Robert WÄ
s <[EMAIL PROTECTED]> wrote:
>
> In the examples that i know i not found solution how persist complex
> objects in server side (for me sql) storage. For example following
> structure:
> Group
> -name
> Product
> -name
> -imageURL
> -price
> Model
> -color
> Group has 1...n Products, Product has 1...n Models
> Temporary i have VO for every objects, but VO are bloated if i use it in
> different context, for example sometimes my Product should has image
> I manage that structure view in swf but if i want persist them that
> should i do - just send whole tree to server via VO and create sql
> queries? I use cairngorm, amfphp.
>
> --
> Robert Was
>
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
