Hi, sorry if this is too vague for the list... but I had an odd dream last night about using grammars to enforce API structure...
I remember there was an effort years ago when component based development hype was at its peak that one way to define components was in the way they interact with one another (which fell down because in describing that in detail, you're essentially implementing the internals)... but nevertheless... clients don't really "command/ask" servers simple questions... api calls follow patterns, individual calls make up sentences. Just taking it from a security angle, given a particular authenticated role, wouldn't a grammar based description of how which api's can be called be a major improvement over the current situation (and quite a useful abstraction)? The key of course is in the stateful/contextual nature of the state machine which would parse the api requests as tokens and validate whether the interaction patterns are valid. Has anybody heard of anybody doing something like this? Was it a success? Thanks, Ben List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address -- You received this message because you are subscribed to the Google Groups "il-antlr-interest" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/il-antlr-interest?hl=en.
