The more I think about question 1, perhaps it is a stupid question that doesn't fit into the REST approach/paradigm. I suppose it would need to be a post to support such a large number of paths/webIDs.
Perhaps a better way to accomplish this would be by configuring the 2000 tags that we needed snapshot values for to be element attributes, then requesting attributes values for that element.
Still would like to know how to do (2), the ability to do adhoc PEs via the PI web services was very useful functionality.
Not a stupid question at all. You've identified the conundrum-- that doing simultaneous requests across multiple resources isn't as straightforward in the REST world as it is in the SOAP world. In SOAP, you define your request/response to do whatever you'd like. In REST, a GET implies that you're accessing a single resource. It's possible of course to define a resource that is a collection of resources. We're struggling with the best way to model these interactions in PI Web API. We'd like to build patterns that are repeatable and easy to anticipate across the surface area. Hence why you won't see it in the first release. Rest assured (and pardon the pun)-- we're actively working on this internally.
As to your second question-- we unfortunately will not support Performance Equations in our first release. A good potential workaround is to define an AF attribute that performs the calculation. This way, common calculations can be written, debugged, and maintained in one place for reuse across the PI System (in DataLink, ProcessBook, PI Web API, and more!)
Thanks Brad! I would be very interested to see how you handle this. I think one possibility would be something similar to the Batch request as defined in oData?(www.odata.org/.../batch-processing)
The problem with the AF Formula workaround is that it is really powerful to not have to define calculations in advance. DataLink 2014 handles PEs really nicely, you can do them on PI tags or AF PI Points, as long as they are all from the same server. I would hope to see this in WebAPI at some point:)