brad's life - named parameters.... CS rocket science, apparently [entries|archive|friends|userinfo]
Brad Fitzpatrick

[ website | bradfitz.com ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

named parameters.... CS rocket science, apparently [Aug. 1st, 2005|03:05 pm]
Previous Entry Share Next Entry
[Tags|, ]

Has nothing been learned by the blogging community about web services?

As if the Blogger and metaweblog API weren't bad enough with positional parameters (which were then overloaded with magical means, like <subject> in the body positional parameter meant a subject was included, which was then parsed out), we now have blo.gs or whoever extending the "ping" API with "extendedPing" which just adds more positional parameters.

What's so hard about named parameters? That's a "hash" or "dict" or "collection" or "associative array" depending on your language. *sigh*
LinkReply

Comments:
[User Picture]From: brad
2005-08-02 05:15 pm (UTC)

Re: extendedPing

(Link)

and the extendedPing interface was defined over four years ago, it's not exactly a recent extension.

Nothing better's come along?

So far the pinging community isn't impressing me. Both blo.gs and technorati won't even support connection keep-alive on their rpc servers, so LJ can't even ping them at a fast enough rate, and I'm wondering if it's even worth it, considering the only pings I see in a lot of these services updated lists are spam.
From: jimw
2005-08-02 05:27 pm (UTC)

Re: extendedPing

(Link)

the best thing for livejournal to do would be to publish a stream of updates as in the blo.gs cloud/feedmesh interface. it's also a sort-of-wonky format, but it makes a lot more sense than doing a ping on every update.

pubsub.com also supports the cloud/feedmesh interface - you can connect to port 9999 on sandbox.pubsub.com to see what it looks like.

the spam problem is not being fought very well. looking at the new blogs at blo.gs, the current prolific spammers appear to be coming in via weblogs.com, as usual.