On Oct 6, 2005, at 1:26 PM, Allen Gilliland wrote:
the only thing i see potentially worth concealing in that url is the
actual anchor, and you could conceal that by using the entryid rather
than anchor, which is something i think we should make possible
anyways.
One of the design goals for Roller was to keep raw database IDs out of
the public URLs produced by Roller. I've always thought it was OK to
use them within the editor UI, but for permalinks I think we need to
stick with handles and anchors and other identifiers.
Some users have asked for numeric anchors (different from the DB id),
which I think is a good idea. So, post number one would have anchor 1,
two would have 2, and so on.
So we'd have:
myserver.com/roller/page/foo?entry=434
instead of:
myserver.com/roller/page/foo?entry=i_hate_microsoft
- Dave
what else would need to be changed?
-- Allen
i think there are actually 2 action items here. (1) provide a good
SSO
structure so that a roller admin could easily define what happens
when a
user transfers from another application into roller and (2) provide
a
good way for roller to be remotely administrated, possibly via
secure
web services. by remotely administrated i mean ... register users,
create weblogs, reset account info, etc. we do this stuff at Sun
right
now, but we've just hacked a backdoor for roller and really this
should
be flushed out into a full feature.
ahhh... a nice remote interface would be awesome. so much to do, so
little time.
I've been giving some thought to a Admin API that is based roughly on
the same fundamental design concepts as the Atom Publishing API. It
would be great if we could come up with a mechanism that could be
implemented across multiple blogging platforms.
- James
