Frank Reese (kinglink) wrote in lj_clients,
Frank Reese

I'm a young developer looking for some pointers into where to start on a client API/other interface
I recently got some free time, and I have wanted to do some programming of stuff that I want, to sharpen and gain skills, as well as to build tools for X and Y. (being unknown objects and quantities at the present). I've a few interests currently but none have really jumped any great ideas at me, however I've wanted to look into programming some widgets for communications to websites/servers, I've done quite a bit of work regarding Client Server programming, however at the time I have programmed both or had full access to both source codes (trial and erroring, with access to both server and client)

One thing that has interested me is LJ, I've a decent sized journal here, and I've thought at one point. "damm I've always wanted to have an archive this thing" as flipping through all the pages tends to grow weary as when I started making a journal I was verbose and "previous 20 entries" appears to only go back 60, which doesn't help too much, and then of course 1+1 added up and I figured that I'd like to look into some sort of client widget program.

Basically I need a little more advice about the site and how to write this. Will I actually need the XML-RPC or just HTML? (I'm using C++ and have a decent grasp on Socket and reading them, though less on actual HTML) So now I'm wondering will I be using the RPC interface (I didn't notice anything there for getting actual entries, so I get the feeling it might be a mixture, but there's some functions that might be helpful if for more advance stuff there's no pages for as well as stuff for getting which days I've posted on)

Should I focus on learning how to do the actual HTTP POST calls, look into the XML-RPC (I've never used XML) or is there another step I should take before jumping into either of those? I've a great grasp of C++, as well as Java, and socket programming, I can code HTML (though my pages tend to look like yawners) but as I meantioned never worked that much on HTTP calls through sockets or such.

I was hoping to use this for this site, and for the most part just be a learning experience for me, as well as a way for me to show off some skill in case I need an example of work for a future employer (unfortunately my current work is either one sided (client that have no servers) and/or confidential depending on which projects I'm talking about) I'm not yet thinking about anything the size or shame of a full client, though if it goes well, there's definitely a possibility I may consider that if the systems/layers and me mesh well.)

Anyways there's basically a road map of stuff I'm considering, any advice on where to really get started if I'm going to actually move towards this "archiver" (There's a couple other projects in my mind, though this one is one I'd actually love to use at some point)

I appreciate any comments and help. Thank you in advance.
  • Post a new comment


    Comments allowed for members only

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened