I've already been mentally plotting out the second method, storing an image sequence in a database. You'd get a URL containing the ID# of the stored sequence. A database would nicely support the ability to chain together multiple animation sequences. Like I figured, this all implies a registration system so you can see just your own stored animations and not be inundated by everybody else's.
cough *SQL* cough *SQL*
whew, excuse me ;-)
of course the database you describe would not require something as robust as sql, if it were installed, seaerchable history would be a sinche. I could take an out of the box perl parser I've already written for my current project here. it would only be a table of five rows not counting the index (name, date, subject and body, and message number) and could be set up alongside our current message structure, we would not have to touch the messages themselves ( although if we ever decided to it would be relatively easy )
I'd also add, even though on the technical side I am sure you already have a solution, but php has the gd library for creating dynamic images, and it supports gifs. . .
Best
-Justin
Space/Science » in reply to Thanks very much!
re: Thanks very much!