PUT for Atom or DELETE

The Atom-Protocol list has fallen down the X does not support PUT and DELETE hole again. I've only been on the list a short time, so I'm talking from a position of extensive ingorance, but I get the impression this is one of several issues that keep coming back like bad mothers in law.    (PYP)

I don't really get it. The current bugaboos are "low-rent" hosting and J2ME. A low rent hosting solution is generally defined as a one stop cheap shop for getting your blog up on the internet on which the user has little control of their environment (such as the web server configuration) and the web server does not, for some reason, allow PUT and DELETE.    (PYQ)

J2ME, I assume, is a problem because released code, out there on already deployed phones, was written without PUT and DELETE support. Is there some issue that makes PUT and DELETE impractical on the devices, or is it just a misstep in the code?    (PYR)

If it is a misstep in the code, why not keep APP on the straight and narrow, and make APP good enough that the cheap boats will rise to take advantage of it. It's not as if one day suddenly everyone should be able to use APP from every network connected device ever made. That would be nice, but is it necessary? No.    (PYS)

J2ME can be improved, and people who want to Atom on their phones will go hunting for devices or software that lets them. They may even hassle their providers. Or does that not happen any more? We just take what we're given?    (PYT)

I don't know, maybe there's some other complication, completely off my radar, and I'm dumb. It happens a lot.    (PYU)

When I started working on APP support for Socialtext, PUT and DELETE were completely outside our local grammar. So I put it in. Since then we've not quite managed to get APP going (soon), but we've expanded our minds on how to interact with content. REST == Good.    (PYV)

Last week, when Eugene and I started Purple.pm, I wanted to use HTTP-Server-Simple to run the web server for the initial HTTP based API we created. But then I discovered it didn't support PUT and DELETE. So I patched the one line of code, and now there's a new version, and whoo hoo.    (PYW)

Not the same thing, I know, but still...    (PYX)

Posted by cdent at 09:07 PM | Trackback This | Comments (0) | TrackBack (0) | | bl | Categories: Atom

Hueco 1

Went to Hueco Tanks last weekend. It was good.    (PYM)

   (PYN)

More pictures    (PYO)

Posted by cdent at 07:30 AM | Trackback This | Comments (1) | TrackBack (0) | | bl | Categories: climbing

Purple.pm

Last week Eugene swung by after RecentChangesCamp and we took a day to do something we've been talking about for years: We finally made a separate module for handling the PurpleNumber creation and index management that is used in PurpleWiki.    (PYC)

The code is still coming together. Thus far there's a subversion repository with working code at:    (PYD)

The basic functions of the tool are pretty straightforward:    (PYF)

• Give a URL, get a PurpleNumber NID    (PYG)
• Give a NID, get back the URL where the identified node can be found    (PYH)

NIDs are stored in SQLite. The code is written with something akin to a factory class so other data storage implementations will be easy to create.    (PYI)

Accessing the data store can be done through direct use of the Perl library, or through a RESTful server subclassed from HTTP-Server-Simple (thanks to Jesse for releasing a new version patched to support PUT and DELETE).    (PYJ)

Using a central nid index for multiple wikis or other tools that use PurpleNumbers enables TransClusion between those multiple tools.    (PYK)

It's nice to get this going.    (PYL)

Update: There's been a fair amount of updates recently. The commit messages have more info.    (PYZ)

Update 2: Released to CPAN.    (PZ0)

Posted by cdent at 07:19 AM | Trackback This | Comments (0) | TrackBack (0) | | bl | Categories: purple