We have an application that keeps tracks of physical assets, we also have some feature layers that contain features that represent many of these assets, but certainly not all. We already have a field on the feature layer that essentially just is the primary key in a SQL table. SO it's very easy for us to clock on a feature and go retirve the realted info from the SQL database.
We can also very easily send a query that returns only assets matching a list of primary keys we send to the server. That works fine for a few or even dozens of assets.
But my problem arises when I want to return a few hundred assets that match a list of primary keys. The reason being is that the ESRI queries are limited by the length of a URL (2,083 chars), which can very easily be overcome once you start looking for a few hundred assets whose primary key is 10 chars or so.
I have overcome this issue in other parts of our program by create a GUID representing a list of numbers and passing the GUID around, but I obviously don't see a way of passing a GUID to ESRI's services. Have others run into this problem?