Log in

No account? Create an account
ljArchive 0.9.2 - LiveJournal Client Discussions — LiveJournal [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

ljArchive 0.9.2 [Jun. 22nd, 2004|04:04 am]
LiveJournal Client Discussions


ljArchive now supports downloading/browsing/searching comments.  In a nutshell:

  • Added support for downloading/browsing/searching/exporting comments.

  • Added a new plugin that provides comment analysis, both how many comments received from each user and given to each user

  • Entries and comments both displayed in a single view, via the updated HTML template system.

  • Updated loading/saving code - new file format is about 35% smaller and loads approximately 6x faster than the old format.

  • Various bug-fixes from user feedback.
Here are some screenshots of the new functionality:The web site for downloading ljArchive is here.  Those of you with monster journals with 10,000 comments or more, are especially welcome to try this new version, and please let me know how it performs     :)

[User Picture]From: susandennis
2004-06-29 04:31 pm (UTC)
I have yet to get the latest version to work on my home computer. Works fine at the office but not at home and, usually, my internet connection is better at home than at work! Both machines WindowsXP, IE6 and the other version worked fine on the home machine.

Here's the error that your handy dandy error copier copied - any clues as to what I should tweak, reinstall, eat for dinner?

ljArchive Error: Error trying to generate a session: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, String methodName, Object[] parameters)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(String MethodName, Object[] Parameters)
at XmlRpcProxy4844767e-e55c-40c8-a2b8-3675fcced015.SessionGenerate(SessionGenerateParams )
at EF.ljArchive.Business.Sync.GoThread()
(Reply) (Thread)
[User Picture]From: susandennis
2004-06-30 04:22 pm (UTC)
This is making me nuts! I've uninstalled and reinstalled. I've reinstalled the .Net framework and I still get the same error message (only now I get it faster!)... I hate to wipe out my db of entries and I cannot imagine that's causing a problem. Suggestions? I really want to have this at home...
(Reply) (Parent) (Thread)
[User Picture]From: fg
2004-06-30 09:38 pm (UTC)
Hi susan,

I'll have to take a look at it this weekend - the exception info you've provided should be all I need.

The client doesn't yet provide very informative error messages - ones like what you've received will eventually be paired down to things I can control (like a bug in the software) and things I can't control (like livejournal being down), with appropriate messages for each.

In the mean-time, thanks for being patient. You'll hear from me soon!
(Reply) (Parent) (Thread)
[User Picture]From: susandennis
2004-07-01 06:49 am (UTC)
Now that I know you are on it, I got patience to burn. Plus I've got my copy at work for emergencies :)

I did suspect the culpret was LJ so I waited until I could get a good response from LJ for a sustained time and tried LJArchive then but I got the same error.
(Reply) (Parent) (Thread)
[User Picture]From: susandennis
2004-07-07 06:38 pm (UTC)

New Clues

Turns out I am genetically unable to leave anything alone :)

I sync'd up my work version and then brought the xja file home. I replaced the xja that I had on my home computer with the one from work and it loaded fine. So, I clicked on 'sync' and guess what??!!! It Sync'd!!! Brought in the new items since the work archive was created!!!

It's fixed! So, it just wasn't happy with the old xja! Wild, eh? I'm such a happy camper.
(Reply) (Parent) (Thread)
[User Picture]From: fg
2004-07-08 08:51 pm (UTC)

Re: New Clues

That's great! I'm glad it sorted itself out, because every analysis I could do pointed at it being some kind of server glitch.

I'll have to keep an eye out for it and hope the issue doesn't come up again in the future.
(Reply) (Parent) (Thread)