W
wood
Guest
The point about the 'filter' parameter to a ReST interface, is that it is a free-form string, so that it can be interpreted any way you want (in your application). You could use it as a WHERE clause for a dynamic query. You could use it for text searches (i.e. CONTAINS), or as a single primary index value/filter. Really it a s pattern, not a defined API, and as such I am not sure where it should show up in documentation. The AutoEdge Mobile sample is a good place to show an 'example pattern'. At some level, there is nothing that even requires that the OE Mobile front-end use the queryString/parameter with a name of 'filter'. It could be almost anything.
Continue reading...
Continue reading...