I still think the size of the team needs to be as small as possible, even to the point of emaciation. This RSS file is offered to individuals and non-commercial organizations only. Or, if this isn't what Mark was getting at, then it does at least clarify my own thoughts on the matter. But I also didn't agree with him. But the example does give a clear starting point. Obviously using simple triangulation, etc. These are the bits that produces the magic slightly transparent background. But I also didn't agree with him. Mark's example focuses a lot on interface generalization but there's much more to REST, and the web, than this. Prentice Hall Publishing sent me a copy of a book I did a technical review for some time ago. I can agree with Mark that REST does a great deal more to separate concerns compared to SOAP and WSDL but I'd say this goes far beyond fuzzy notions of generic interfaces. They said it had gone missing. It's a good read but it's also a bit confusing. Once such a precipitous cliff is identified it can be carefully avoided it and all is well again. I have a hard time imaging any way to effectively manage a group of people that size working on a single project in any industry. This article explains how to achieve this functionality. I still think the size of the team needs to be as small as possible, even to the point of emaciation. This assumption is also the source of the nausea. I understood just what Mark he was saying but the words didn't really compute. This assumption is also the source of the nausea. Both will probably survive. Thrid and the point of this post is can the old BBS days trick of Wardialing to find connections help in a war? Big Bang projects always seem to attract huge budgets and massive headcount, but there are few companies out there who could even field such a large workforce and invest so many billions. Both will probably survive. This fixes things up. This RSS file is offered to individuals and non-commercial organizations only. This erroneous assumption leads to the broken example and his strange notion of generalization. Which operations invalidate which resources; which PUTs are idempotent, etc. "They were moving slowly over the houses," she said. This assumption is also the source of the nausea. But say this out loud and there's a definitely an uncanniness that hangs in the air. So, programming language is not a set of features, it is a set of restrictions". This assumption is also the source of the nausea. But the example does give a clear starting point. He talks about how he is pleased with Sun's decision and how they're implementing it and how he thinks that Kaffe, GCJ, etc will continue to thrive. The important question is whether REST does separate concerns and, if so, precisely how it achieves such separation. But the example does give a clear starting point. It's been explored by many people in many places at many times. But after the feeling of vertigo induced by Mark's essay it occured to me that perhaps there's still something here.
audience.gif
Description: GIF image
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
