tag:blogger.com,1999:blog-6069439299305224730.post9103944142990533153..comments2023-03-22T15:06:21.232+01:00Comments on zoom.nu: topless objectsAnonymoushttp://www.blogger.com/profile/01044897049984478240noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6069439299305224730.post-67451361703431682262009-05-25T09:47:07.688+02:002009-05-25T09:47:07.688+02:00So some chain-of-command where each stage gets to ...So some chain-of-command where each stage gets to refine the request or contribute to the result? Or actually, I guess the chain will be more like a tree when you have components.<br />Soudns like an interesting idea that I'd be glad to read a follow-up on when you've tried it out ;-) One thing that could be fun to explore is the type of the steps in the chain. For instance, a step that validates the arguments will take a request with string parameters and refine it into a request with typed ones. Later stages must be able to express that they expect a request in this state instead. If every step refines the request or response in a way that the others depend on, then the type of the n:th stage sill be one that takes a request and response in the n-1:th state, and the whole chain setup is reproduced in the type of the last stage. Hopefully it will not be that bad. My hunch is that you will get 3-4 different phases, which gives 2-3 types for the stages on the border between phases and 3-4 types for stages within phases.Anonymoushttps://www.blogger.com/profile/01044897049984478240noreply@blogger.com