posted by ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
pmsumner at 01:48am on 16/04/2002
pmsumner at 01:48am on 16/04/2002URL at the bottom of the page.
All it does so far is parse out the information you get back from the LJ server and present it as tables in an HTML document to your browser. I don't log any inputs to the form, but if you don't trust me - use username: test / password: test .
It won't be at all long now until you can post. It's actually a really simple addition once everything in the background is set up. This has been the bitch, for me. I've had horrendous problems with the moods, because the way that the LJ server returns them is a bit weird, and had to rewrite that code a few times. Currently the moods are cached server-side. I can't decide whether to leave it this way or not. I think it's probably a good thing to.
Making the back end as generic as possible has actually been difficult. I've had to learn several new concepts to make a web interface useful, and had to learn how to manipulate and convert data to HTML, though this has been made much easier thanks to the HTML::Template Perl module.
Check Friends doesn't actually do anything particularly useful - just throws out the info the server has, telling you (in PST) what time your friends page was updated. (I should note that this works in the text mode client) I need to figure out cookies so that I can implement a per-user checkfriends scheme, as it requires storage of a server response between "sessions". This I could store in a username-based file on the server, but it's cludgy and could potentially result in a DoS attack. Storing data on the client machine in user-based cookies is much nicer.
There is very little error checking. As far as I know there's only two ways it can bomb out - firstly there's timeouts, invalid hostnames, or something else network-problem-y. Secondly there's LJ Errors, handling of which is a bit patchy - it simply repeats what the server throws out. If you find any weird errors, please tell me.
The script is slow - I'm not quite sure whether it's the script that's slow or whether there's network congestion somewhere on my host's network. So please wait for output before hitting refresh/submit again.
http://www.philsumner.co.uk/lj_web_client.html
All it does so far is parse out the information you get back from the LJ server and present it as tables in an HTML document to your browser. I don't log any inputs to the form, but if you don't trust me - use username: test / password: test .
It won't be at all long now until you can post. It's actually a really simple addition once everything in the background is set up. This has been the bitch, for me. I've had horrendous problems with the moods, because the way that the LJ server returns them is a bit weird, and had to rewrite that code a few times. Currently the moods are cached server-side. I can't decide whether to leave it this way or not. I think it's probably a good thing to.
Making the back end as generic as possible has actually been difficult. I've had to learn several new concepts to make a web interface useful, and had to learn how to manipulate and convert data to HTML, though this has been made much easier thanks to the HTML::Template Perl module.
Check Friends doesn't actually do anything particularly useful - just throws out the info the server has, telling you (in PST) what time your friends page was updated. (I should note that this works in the text mode client) I need to figure out cookies so that I can implement a per-user checkfriends scheme, as it requires storage of a server response between "sessions". This I could store in a username-based file on the server, but it's cludgy and could potentially result in a DoS attack. Storing data on the client machine in user-based cookies is much nicer.
There is very little error checking. As far as I know there's only two ways it can bomb out - firstly there's timeouts, invalid hostnames, or something else network-problem-y. Secondly there's LJ Errors, handling of which is a bit patchy - it simply repeats what the server throws out. If you find any weird errors, please tell me.
The script is slow - I'm not quite sure whether it's the script that's slow or whether there's network congestion somewhere on my host's network. So please wait for output before hitting refresh/submit again.
http://www.philsumner.co.uk/lj_web_client.html