?

Log in

No account? Create an account
October 16th, 2002 - LiveJournal Development [entries|archive|friends|userinfo]
LiveJournal Development

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

October 16th, 2002

synsuck [Oct. 16th, 2002|09:38 am]
LiveJournal Development

lj_dev

[uncon]
For some reason, I cannot get syndication to work at all on uJournal. Everything seems like it's working, but I don't get new entries. I usually get one or two, then it stops (without returning an error). Here is an example:


Running task 'synsuck':

Synsuck: memepool (http://memepool.com/memepool.rss)
HASH(0x89d78e4)e21dKiuz0cKP8i5BJkxdYw - After a googly, bumper, or a yorker, I think I'd fancy a Scrumpy Jack, guv'nor.
Synsuck: kuro5hin (http://www.kuro5hin.org/backend.rdf)
HASH(0x89de76c) HASH(0x89de950) HASH(0x89de908) HASH(0x89de8c0) HASH(0x89de878) HASH(0x89de830) HASH(0x89de490) HASH(0x89de784) HASH(0x89de61c) HASH(0x89de6c4)YRwCb/S16BedpsltrBP5eg - U.S. pressures Taiwan to extend copyright terms to 70 years with "Disney clause"
Synsuck: theregister (http://www.theregister.co.uk/tonys/slashdot.rdf)
HASH(0x89e7f9c) HASH(0x89c7f00) HASH(0x89de484) HASH(0x89de598) HASH(0x846f288) HASH(0x89d7a94) HASH(0x89c7cf0) HASH(0x89c7e10) HASH(0x89b5f6c) HASH(0x89d7aac)YRwCb/S16BedpsltrBP5eg - Nominet director calls for .net.uk clemency
o3mdA+Jio4Ps/R7ZAaJyNw - Get your g logos here
vcRglbPUBOgWYu47EKSU7g - BOFH: Going Postal
Synsuck: linuxtoday (http://linuxtoday.com/backend/my-netscape.rdf)
HASH(0x89de938) HASH(0x89de4d8) HASH(0x89de9d4) HASH(0x89de80c) HASH(0x89b5fe4)e21dKiuz0cKP8i5BJkxdYw - The Register USA: Linux-Based TMTA Tablet PC for $600?
Synsuck: dotkde (http://www.kde.org/dotkdeorg.rdf)
HASH(0x89de418) HASH(0x89d79d4) HASH(0x89c7d20) HASH(0x89e7fe4) HASH(0x89b5c9c) HASH(0x89de598) HASH(0x89d7ad0) HASH(0x89c7f00) HASH(0x89c7fb4) HASH(0x89b5eb8)e21dKiuz0cKP8i5BJkxdYw - KDE Switches To Bugzilla
Synsuck: wired_news (http://www.wired.com/news_drop/netcenter/netcenter.rdf)
HASH(0x89d7a04) HASH(0x89d7b24) HASH(0x89de730) HASH(0x89de980) HASH(0x89d79a4) HASH(0x89de4f0) HASH(0x89d79e0) HASH(0x8991f00)YRwCb/S16BedpsltrBP5eg - Spectrum Limbo Hurts Wireless Biz


This is the first run after creating those accounts. If I'm not mistaken, it should have pulled every story from each .rdf file. It didn't. "synsuck" is running every 10 minutes (and has been for a day now) and it hasn't retrieved any new stories.

Does anyone know what might be wrong?
link5 comments|post comment

Protocol Documentation Updating Reference [Oct. 16th, 2002|01:06 pm]
LiveJournal Development

lj_dev

[xb95]
Hey everyone.

I figure that the following information might be useful to those of you who write patches. I know that I've had to dig and scrounge to find this information, and compiled it myself. This post outlines the ways to update the protocol documentation as well as how to build the documentation.

If anybody has any changes they can suggest to this document, or anything I have wrong, let me know. I'd appreciate the corrections, as this information is quite useful to me and I'd hate to be using the wrong info!

Thanks.




Documentation Types
There are two types of protocol documentation: flat and XML-RPC. If you're modifying the client protocol, you're going to have to modify both modes inside ljprotocol.pl, so you're going to have to modify both sets of documentation. If you don't do both, your patch will likely get rejected by the powers that be. I've found this out the hard way, heh.

Updating Flat Mode Documentation
This is the easier of the two types to update. Basically, all you have to do is modify the file htdocs/protocol.dat. It contains all of the flat modes in a fairly easy to understand format. I won't tell you how to modify the file--take a look and figure it out for yourself.

If you are creating an entirely new protocol mode, you can simply append it to the end of this file. Simple.

Updating XML-RPC Documentation
If you are simply making a change to an existing protocol mode, then you will need to modify the file doc/raw/build/protocol/name.xml where name is the mode. For example, if you want to make a change to the getevents protocol documentation, you'd modify the file doc/raw/build/protocol/getevents.xml. Once again, the actual format of the file will be up to you to decipher. It's not that hard, it's kinda like HTML.

On the other hand, if you are creating an entirely new protocol mode, you will need to do two things. First, create an XML file named mode.xml and put it in the doc/raw/build/protocol/ directory. You will need to model this file after the other XML files already in the directory. Take a look at them to find out how to structure your file and the particular elements to use. The second thing you will need to do is modify doc/raw/build/protocol/xmlrpc.xml. You should see a bunch of <!ENTITY ...> lines near the top; add a line like this after them:

<!ENTITY mode.name SYSTEM "name.mode.xml">

Replacing name with the name of your new protocol mode, of course. Then, scroll down some in the file until you see &mode... lines. Add a line like this:

&mode.name;

Now, save the file and close it. You're done.

Generating the Documentation
I will assume, for the sake of discussion, that everyone is using goathack. If you aren't, then the procedure should be the same, but you're going to have to experiment on your own.

You will need to generate the docs every time you update any of the document files. This is a rather slow and tedious process--goathack will need 5-10 minutes to do it, depending on server load at the time.

It's a very simple command:

~/doc/raw/build/generate.pl --myxsl

The --myxsl option instructs generate.pl to use the version of XSL (or whatever it's called) installed on the server. The version installed works just fine with generate.pl, there's no need to try to get a new one or anything.
link1 comment|post comment

navigation
[ viewing | October 16th, 2002 ]
[ go | Previous Day|Next Day ]