What the client is is basically a set of 4 pages.
Page 1: Login to the client. Which loads the default "blurb" for the artist's main site (if any), and the default subject field.
Page 2: Fill out URL to latest strip and optionally change the blurb and subject fields.
Page 3: Preview Page of how the comic entry will look (Sample:
[Blurb] ) along with the last button to confirm posting to the journal.
Page 4: Confirmation page with any error messages LJ.com may have spit back.
Now, I've just been tossing this around against log.cgi and it all works, but log.cgi spits back text/plain and what I'm looking for is text/html. (Unless any of you know a way perl can simulate a POST action to another script and then wait for the return). So what I'm thinking is possibly modifying log.cgi into something that will do the queries (log in, post event, etc) and then send the info back to my comic.cgi (via GET method likely) to display page 4.
So I have two questions.
1) Having a custom log.cgi (I'll call it comic-log.cgi from here on) to make queries/updates on the artist table, as well as log in the user and post the event would seem to be very useful. It also minimizes what scripts have to run on lj.com. Would this be advantageous to having the actual client.cgi on lj? (the client.cgi would basically just be a script that displayed HTML forms and then compiled that data into a single event for posting)
2) The data for the artists is important. Most artists don't know HTML or don't have the time to add in the same blurb to every entry. So having a table for artist info is needed. Should this be on the LJ.com server? And access it via the comic-log.cgi? Or should some other server be found to host this data?
Any comments and questions on this are greatly appreciated. Ciao.