Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 128

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 134

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 141

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 169

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 199

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 205

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 233

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 248

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 254

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 267

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php on line 595

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/files/model/_file.funcs.php on line 559

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_connect_db.inc.php on line 29

Strict Standards: Declaration of UserSettings::get() should be compatible with AbstractSettings::get($col_key1, $col_key2 = NULL, $col_key3 = NULL) in /home/fumanchu/webapps/b2/blogs/inc/users/model/_usersettings.class.php on line 208

Strict Standards: Declaration of UserSettings::set() should be compatible with AbstractSettings::set() in /home/fumanchu/webapps/b2/blogs/inc/users/model/_usersettings.class.php on line 208

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_core/_param.funcs.php on line 1692

Warning: Cannot modify header information - headers already sent by (output started at /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php:128) in /home/fumanchu/webapps/b2/blogs/inc/sessions/model/_session.class.php on line 219

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/generic/model/_genericelement.class.php on line 109

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_core/model/dataobjects/_dataobject.class.php on line 428

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_core/model/dataobjects/_dataobject.class.php on line 437

Strict Standards: Declaration of Blog::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/fumanchu/webapps/b2/blogs/inc/collections/model/_blog.class.php on line 1886

Strict Standards: Declaration of Group::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/fumanchu/webapps/b2/blogs/inc/users/model/_group.class.php on line 553

Strict Standards: Declaration of User::dbdelete() should be compatible with DataObject::dbdelete() in /home/fumanchu/webapps/b2/blogs/inc/users/model/_user.class.php on line 1343

Strict Standards: Declaration of User::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/fumanchu/webapps/b2/blogs/inc/users/model/_user.class.php on line 1343

Strict Standards: Declaration of Filetype::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/fumanchu/webapps/b2/blogs/inc/files/model/_filetype.class.php on line 192

Strict Standards: Declaration of Comment::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/fumanchu/webapps/b2/blogs/inc/comments/model/_comment.class.php on line 1334

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/_blog_main.inc.php on line 412

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/items/model/_itemlist.class.php on line 483

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/items/model/_itemlistlight.class.php on line 119

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/items/model/_itemlistlight.class.php on line 838

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/items/model/_item.class.php on line 1411

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/items/model/_item.class.php on line 1414

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/items/model/_item.class.php on line 3000

Strict Standards: Declaration of ItemListLight::query() should be compatible with Results::query($create_default_cols_if_needed = true, $append_limit = true, $append_order_by = true, $query_title = 'Results::Q...') in /home/fumanchu/webapps/b2/blogs/inc/items/model/_itemlistlight.class.php on line 48

Strict Standards: Declaration of GenericCategoryCache::clear() should be compatible with DataObjectCache::clear($keep_shadow = false) in /home/fumanchu/webapps/b2/blogs/inc/generic/model/_genericcategorycache.class.php on line 375

Strict Standards: Declaration of GenericCategory::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/fumanchu/webapps/b2/blogs/inc/generic/model/_genericcategory.class.php on line 133

Strict Standards: Declaration of CollectionSettings::_load() should be compatible with AbstractSettings::_load($arg1 = NULL, $arg2 = NULL, $arg3 = NULL) in /home/fumanchu/webapps/b2/blogs/inc/collections/model/_collsettings.class.php on line 130

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334

Notice: Array to string conversion in /home/fumanchu/webapps/b2/blogs/inc/_core/_param.funcs.php on line 1161

Notice: Array to string conversion in /home/fumanchu/webapps/b2/blogs/inc/_core/_param.funcs.php on line 1161

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334

Warning: Cannot modify header information - headers already sent by (output started at /home/fumanchu/webapps/b2/blogs/inc/_main.inc.php:128) in /home/fumanchu/webapps/b2/blogs/inc/skins/_skin.funcs.php on line 379
I don't get PUT versus POST

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/widgets/model/_widget.class.php on line 451

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/inc/widgets/model/_widget.class.php on line 547

Strict Standards: Declaration of ComponentWidget::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/fumanchu/webapps/b2/blogs/inc/widgets/model/_widget.class.php on line 722
« 36 hours of fun and sunPeople movers writ large »

I don't get PUT versus POST

07/05/05

Permalink 03:00:51 pm, by fumanchu Email , 292 words   English (US)

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334
Categories: IT


Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334
I don't get PUT versus POST


Strict Standards: Declaration of markdown_extra_plugin::GetDefaultSettings() should be compatible with Plugin::GetDefaultSettings(&$params) in /home/fumanchu/webapps/b2/blogs/plugins/_markdown_extra.plugin.php on line 84

Strict Standards: Declaration of smilies_plugin::GetDefaultSettings() should be compatible with Plugin::GetDefaultSettings(&$params) in /home/fumanchu/webapps/b2/blogs/plugins/_smilies.plugin.php on line 398

Strict Standards: Declaration of smilies_plugin::GetDefaultUserSettings() should be compatible with Plugin::GetDefaultUserSettings(&$params) in /home/fumanchu/webapps/b2/blogs/plugins/_smilies.plugin.php on line 398

Once in a while, I'll run across posts like Benjamin Carlyle's on REST topics, where the author advocates minimal use of POST, instead preferring PUT for almost every request that has an enclosed entity.

Hogwash. That works fine for blogs and forums, but for real CRUD apps, POST is perfectly fine for updating a resource:

The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request identifies the entity enclosed with the request -- the user agent knows what URI is intended and the server MUST NOT attempt to apply the request to some other resource. If the server desires that the request be applied to a different URI, it MUST send a 301 (Moved Permanently) response; the user agent MAY then make its own decision regarding whether or not to redirect the request.

In other words, a URI handles a POSTed entity, but is or becomes a PUT entity. When I make a CRUD app, most of my URI's are "entities that accept annotations". It is a very rare operation for me to replace entire entities.

Or perhaps, I'm just thick. Maybe, Fielding is asking me to expose each attribute of, say, an Invoice resource as its own subordinate resource, with its own URI? But that way lies madness, IMO.

So, stealing the layout from Dave Megginson:

CRUD HTTP
Create PUT
Retrieve GET
Update POST
Delete DELETE

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/skins/_item_feedback.inc.php on line 156

3 comments

Comment from: Benjamin Carlyle [Visitor] · http://members.optusnet.com.au

Strict Standards: Only variables should be passed by reference in /home/fumanchu/webapps/b2/blogs/inc/plugins/model/_plugins.class.php on line 677

Strict Standards: Declaration of PluginSettings::get() should be compatible with AbstractSettings::get($col_key1, $col_key2 = NULL, $col_key3 = NULL) in /home/fumanchu/webapps/b2/blogs/inc/plugins/model/_pluginsettings.class.php on line 95

Strict Standards: Declaration of PluginSettings::set() should be compatible with AbstractSettings::set() in /home/fumanchu/webapps/b2/blogs/inc/plugins/model/_pluginsettings.class.php on line 95

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334

Strict Standards: Only variables should be passed by reference in /home/fumanchu/webapps/b2/blogs/inc/plugins/model/_plugins.class.php on line 677

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 236

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1030

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1030

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1053

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1729

Hello.

My piece was really about the intersection between REST and Object Orientation. REST essentially says "you should have few verbs and few content types, but many names". My view at present is that each verb should have understandable semantics from the client's perspective, particularly as they relate to the resource you're operating on. The wider semantic implications of the change are left to the server, and it is up to the client to be as aware as necessary of these extra semantics.

Outside of this REST perspective I don't have any comment on the use of POST. Within it, I see the need to for its semantics to be nailed down. The semantics I would currently apply to the traditional verbs are as follows:

GET: Get the state of an existing resource.
PUT: Make an existing resource assume state consistent with put content.
DELETE: Delete an existing resource.
POST: Create a new resource with state consistent with posted content.

I would rewrite your table as:
Create = POST
Retreive = GET
Update = PUT
Delete = DELETE

There are other ideas in play about how these verbs should be interpreted, but I think my rules are a consistent and complete set. I don't think the semantics of your table are well-defined for POST. I think that "handle" is too vague a term.

You say in your article, "When I make a CRUD app, most of my URI's are "entities that accept annotations"". I would be more specific, and say "most of your URIs are resources that create other (annotation) resources". In this sense, you are using POST in the same way as I proscribe. I would generally see the kind of URI you POST to as being different to the kind of URI you PUT to. One is like a factory, and the other a regular object.

Thanks for your feedback :)
Keep it coming.

Benjamin.

07/06/05 @ 10:07
Comment from: fumanchu [Member] Email

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1030

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1030

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1053

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1030

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1030

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1053

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1729

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1729

Thanks for the comments, Benjamin!

One is like a factory, and the other a regular object.

Mark Baker has used the terms "container" and "resource" to mean the same thing, I think. http://www.markbaker.ca/2002/08/HowContainersWork/

However, I diverge from his model, wherein he says, "...most resources are also containers. That is, for every resource, you can conceptualize a reason for it to also be a container for something." You said essentially the same thing above ("most of your URIs are resources that create other (annotation) resources"). That isn't true for my apps--most of my domains have very flat objects (Directory, Invoice, Inventory, ...) that are related to each other, rather than being contained by each other.

That doesn't bear on the choice of PUT vs. POST, however. ;) But I think I understand your point-of-view better. In particular, I can see how PUT applies more often to an existing resource, whereas POST applies more often to a container. The fact that containers are resources doesn't help much. :/

Hmmm...

07/06/05 @ 10:49
Comment from: Vitto [Visitor]

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1030

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1030

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1053

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 721

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/fumanchu/webapps/b2/blogs/plugins/markdown_extra/markdown.php on line 1729

I hope that since the date this article has been published you got a deeper knowledge of PUT and POST.

Anyway, you should read this:
http://jcalcote.wordpress.com/2008/10/16/put-or-post-the-rest-of-the-story/

Best

11/02/09 @ 12:06

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/skins/_item_comment_form.inc.php on line 67

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/skins/_item_comment_form.inc.php on line 84

Leave a comment


Your email address will not be revealed on this site.

Your URL will be displayed.

Please enter the phrase "I am a real human." in the textbox above.
(Line breaks become <br />)
(Name, email & website)
(Allow users to contact you through a message form (your email will not be revealed.)

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/plugins/_calendar.plugin.php on line 190

Deprecated: Assigning the return value of new by reference is deprecated in /home/fumanchu/webapps/b2/blogs/plugins/_calendar.plugin.php on line 905

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 334
December 2020
Sun Mon Tue Wed Thu Fri Sat
 << <   > >>
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    

Search

The requested Blog doesn't exist any more!

XML Feeds


Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 223
multiblog

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 304

Deprecated: Non-static method Hitlist::dbprune() should not be called statically, assuming $this from incompatible context in /home/fumanchu/webapps/b2/blogs/inc/sessions/model/_hit.class.php on line 531

Warning: Creating default object from empty value in /home/fumanchu/webapps/b2/blogs/inc/settings/model/_abstractsettings.class.php on line 304