I posted this last week, but I think I did not phrase all of it correctly.

Can flash write an xml file which can be sent through php which then logs the
xml file in the database and names the xml file with an id.
the newly named xml file is then written on the server by either php or mysql?
Can mysql delete this xml file after a certain date?

Reason: I want to create ecards that have ALOT of variables. I would like to
keep it all in the xml file instead of logging it in the db. When the user
picks up his/her ecards, then flash would be able to import the newly named id
xml file and not go through all of the php etc...

Please let me know if this is possible. I'm trying to find the most efficient
way to do this.

Thank you,
Emma

Thank you so much for your taking the time to write me. I left out an
essential ingredient. The flash interface is on a DVD which will then contact a
server. Then the server will send out an ecard.
So the xml thing is just too much..ok....thank you.

Let me know if this changes things.

thank you!
Emma

The XML part seems overkill to me. First of all a setup Flash/PHP/MySQL can
handle a lot of variables. Secondly, I would like the framework to be as
compact as possible. Any additions leave room for error. If you really want the
extra XML-part, it's best to use the filesystem functions of PHP to write, read
and delete the XML-files. Is there a compelling reason to store this
information in the database? Maybe you just need to store a pointer to the
XML-file.
Based on your description you might want to have a look at Remoting.

Then you should do the research on the Flash Player security policy. As you
know when you make a call to the server, the Flash Player will look if the swf
and the script you call are on the same domain. If not, it will look for a
cross domain policy file which grants access to the Flash Player. Personally I
don't know how this works for stand-alone app's but my advice is to check this.
On the XML-part: by all means, if you feel comfortable with it, just go ahead.
My idea is that you can skip this part but consider that it is based on a short
description of your app.