?

Log in

No account? Create an account
January 27th, 2001 - LiveJournal Development [entries|archive|friends|userinfo]
LiveJournal Development

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

January 27th, 2001

(no subject) [Jan. 27th, 2001|12:18 pm]
LiveJournal Development

lj_dev

[muerte]
Anybody know a good way to sort a collection in VB? I have my sync client working and downloading entries, but if you update an older entry (correct spelling or something) when it re-downloads the updated entry it puts it at the bottom of the list. So 99% of the entries are in order chronologically except for the last couple which are updates. So I just need a simple way to sort the collection, probably by date so when it goes to write all the entries from memory to disk it puts them in the right order. I'm open for suggestions.
link2 comments|post comment

Friends page update notification in clients [Jan. 27th, 2001|11:11 pm]
LiveJournal Development

lj_dev

[mart]

We've seen the new mode=live thing you can now do on your friends page, which refeshes a small frame with some JavaScript in it and thus only updates your friends page when there is a change. I now propose a protocol addition to do similarly!

The client would just make a simple request, say mode=checkfriends&user=test&password=test, and the server would reply with a single variable set to either 0 or 1 depending on whether there has been a change. The clients can make this request at minimum every 30 seconds, and this will be enforced on the server-side by rejecting requests more often than that from the same username. This won't actually stop it being made more than every 30secs, but it would at least make it pointless so there's no advantage to it. Since the server would have to 'remember' the last time the client checked, this also has the advantage that the client doesn't have to send this every time.

What the client does next is up to itself (or its settings). The Win32 client, for example, could show a simple anim of the little pencil scribbling, spinning or such. Failing that, a dialog could simply be displayed. The client should at this point cease making the request periodically, since it knows there has been an update. This will mean that people with permanent connections who leave their clients running all day when they aren't around will at least stop making this request at some point!

I believe this is the best way to do what is at best a dirty hack (as is mode=live!), but of course feel free to suggest improvements, or tell me I'm a fool.

link11 comments|post comment

navigation
[ viewing | January 27th, 2001 ]
[ go | Previous Day|Next Day ]