... Sorry I should of been clearer, I agree that that's what the spec says, I was describing how I'd like it to be structured. Conveniently though, I can post...
... Agreed. Maybe a way to structure the specification would be to say that the new URL MAY/SHOULD appear under the URL you POST to. I.e. give guidance on best...
... sounds good. ... I'll have to put it on the "to review" pile. ... I posted the server side code, the client code is still too rough, but i think the server...
I heard Simon had problems running Joe's RESTLog server written in Python against Apache under RH and another OS... I have tried it against IIS 5.0 under...
Simon: I finally checked out your RESTLog server for .NET (http://www.pocketsoap.com/weblog/stories/2003/04/0020.html). Sweet! Very elegant code, IMHO. As a...
Ok, played with joe's client and simon's server and while I can POST new items, I find that I can't to any updates or deletes since joe's spec indicates...
... Correct. The problem is that my RESTLog client makes some assumptions about the server which are not in the spec. I need to update the client to remove...
In continuing to play here, I've noticed that simon stores posts as <item> <title> <description> <dc:date> </item> and joe's example shows the post as: <item> ...
Understood. Just wanted to encourage a way to 'spec' this out in a way that others can extend their client and server implementations without everyone having...
... That's an interesting question because it can also affect the way item fragments are initially send from the client side to the server side of the ...
... That might indicate that RESTLog.cgi is crashing. ... Could you print out the content of the response above? RESTLog uses the Python library 'cgitb' which...
Well, I'm almost with you there. On a POST, the <link> is not needed since computing it will happen on the server. For PUTs it *might* be needed, but I suspect...
... I had RESTLog.cgi crashed once (I did not set the data directory appropriately) and had back an error message. ... That's an interesting question... I've...
... It may be someting in IIS, as there's nothing programmatically in RESTLog.cgi that would produce a '100 Continue'. -joe -- http://BitWorking.org ...
... Its my understanding that Link doesn't have to be the link to the page for the post, it may be a link that the post is commenting on. [At least, this is...
... IIS typically will send a 100 Continue in response to a HTTP/1.1 request. This shouldn't cause any problems, its a manditory part of the HTTP/1.1 spec. I...
... In RSS-1.0 the rdf:about on an <item> is for the ITEM itself. The <link> element CAN be EITHER that same link (as a permalink) or as a single link to some...
... Yes. But I also tried using HttpClient with setHttp11(false) in order to use HTTP/1.0 and avoid the 100 Continue response (since HTTP 1.0 did not define...
... This sounds like the behavior i was seeing on Apache2/W2k, i can see the python exe process start up, but it never goes away, and i never get a response...
... I updated the CommentAPI recently but forgot to add the same verbage to the RESTLog spec. That is: The contents of the 'item' element are guided by the <a...
... On the other hand, I managed to have Bulu (let's call things with their proper names ;)) up and running under Windows 95 against Apache 1.3.20. I got a...
... So, since it is not required to have a valid RSS item fragment, I have removed the fake <link> element from my client implementation, accordingly to the...
This list has been far too quiet and that is mostly my fault. The topic of Weblog API has been quite a topic of discussion that I've chimed in on through my...
... Things wax and wane. Mailing list traffic and energy especially. Don't blame yourself :-) ... Depending on the questionee's leaning, this question answers...
... Personally, I'd not go on the XML-RPC path, especially if the so-called Weblog API (more on names in a few paragraphs) is something we want to be widely...
Hi all. In the RESTLog interface specification I did read: "Type is just a shorthand for the mime-type of that transaction. Normally selecting the mime type is...
perhaps its just a typo, but a conneg request should sent an Accept: header to indicate the acceptable response types, not a content-type. On the otherhand, i...
... It is actually the Accept: header that drives content negotiation on a GET. The Content-Type: header is used on the PUT and POST. The ?xml is designed to...
... Yes, it is, as also Simon pointed out correctly. But, issuing the following HTTP request to your weblog on bitworking.org: GET /news/PyTextileAndBulu...
... Ok, now I understand. That could best be described as bug, the code where I determine the mime-type doesn't know the verb, GET, PUT, POST, etc. It just...
