tag:blogger.com,1999:blog-7618276.post1490134174918175260..comments2024-03-14T05:19:03.379-05:00Comments on Koranteng's Toli: Crawl Before You WalkKorantenghttp://www.blogger.com/profile/05280138409675883100noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7618276.post-67255955487003617402007-04-18T13:58:00.000-05:002007-04-18T13:58:00.000-05:00Ed,I'll be sure to give feedback, and through the ...Ed,<BR/><BR/>I'll be sure to give feedback, and through the right channels. I'm actually now in a job where this kind of thing is part of what I'm supposed to be doing. Previously, and sadly so, there was no incentive, and a developer's time is too limited.<BR/><BR/>I won't quibble with JSF's previous use of POST, like you suggest, given the model, it was the right thing to do. I think however that there is a further point to be made and that is about the model.<BR/><BR/>The process I've suggested is: first, identify all important resources, then figure out the correct verb. <BR/><BR/>It seems to me that this is part of the analysis that is now being done for JSF 2.0. There are undoubtedly important resources that weren't identified previously. Moreover, for some of these resources, there are likely operations that could deal with an HTTP GET (allowing bookmarking and caching to take place) or perhaps even a PUT. Of course your mileage might vary but a thorough examination of the lifecycle is warranted. <BR/><BR/>The thing however is that the analysis needs to be done. When folks approach me about REST issues, I always say start with Resource Modeling.<BR/><BR/>To paraphrase a gospel writer<BR/><BR/><B>"Seek ye first the resource model and his righteousness; and all these things shall be added unto you."</B>Korantenghttps://www.blogger.com/profile/05280138409675883100noreply@blogger.comtag:blogger.com,1999:blog-7618276.post-39138763554164868202007-04-18T12:50:00.000-05:002007-04-18T12:50:00.000-05:00Hello Koranteng,Thanks for your comments on the JS...Hello Koranteng,<BR/><BR/>Thanks for your comments on the JSF 2.0 draft. While I'm glad to hear you think we're on the right track, I want to point out that JSF's usage of POST for all interactions with the lifecycle is in fact correct with respect to <A HREF="http://tomayko.com/articles/2004/12/12/rest-to-my-wife" REL="nofollow">REST</A>. <BR/><BR/>POST should be used when idempotency cannot be guaranteed. Because the standard JSF lifecycle had no way of guaranteeing idempotency, it made sense to always use POST. <BR/><BR/>In JSF2, I expect we'll have some mods to the lifecycle that will allow us to make the guarantee.<BR/><BR/>Finally, I urge you to get in touch with Mr. Stephen Kenna, IBM's rep on the JSF Expert Group. I would greatly appreciate having your JSF feedback flow through him to the JSF expert group.edburnshttps://www.blogger.com/profile/14048196581438285965noreply@blogger.com