Mark Baker wrote: > Web services are non-scalable because the complexity of a system with > arbitrary interfaces is far too high. It's a complete show-stopper > unless you control both ends of the interaction, in which case it's > just a lot more work than is necessary.
This is where I don't understand at all. How can data produced by a restful/http system be any more well defined or any more able to be cooerced than data produced through any other system. In order to use a URL, you have to know what it is and imbed it somewhere. This is identical to knowing the name of the interface in an RPC system. Once you know the interface, you know how to find the methods which are defined. Only if you know that HTTP is involved do you know what the operations might be (WATCH was mentioned and other custom functions exist in internal web servers). The parameters specified in the argument list of the methods in the interface are identical to knowing the appropriate mimetypes and data that can be used for any put/post/get/delete/... http operation. Help me understand how there is a measurable difference in complexity here. Gregg Wonderly ------------------------ Yahoo! Groups Sponsor --------------------~--> Yahoo! Groups gets a make over. See the new email design. http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
