From the small number that I know about WCF, this seems to be the correct solution to the specific problem that I have, but I would like to get some input on it.
Description of the problem:
Clients sequentially gain access to domain objects from the list approximately once in 1-10 minutes (on average 2 minutes), but none of the 2 clients should access the same object. The list must support certain orders.
Usage example:
Client X -> WCFService::GetNextObject() -> Fetch from DB, sort
<- return nextObject
Where X is [1,~200)
The list of objects is basically a database table where each object is annotated with priority. All objects with priority 1 should be as follows. The order from there depends on the priority level. For instance. Priority 1 object must be given in chronological order based on the date and time for the object, while priority 4 objects must be transferred in alphabetical order based on the string value on the object.
[Change] Some clarification points: there are other sorting schemes for different priority levels that should refer to related records in a myriad of other tables - this seems overly complicated, but there is a real business example for this. Similarly, objects are added and removed from this list potentially very often (but the average value is rare). [/ Edit]
WCF, LAN/WAN, , nextObject. , WCF - ?
, , WCF? , : ? WCF? , /?
, .NET, , , .NET. .