c# - Is WCF the right choice for me? -


What I know about WCF is the correct solution to this particular problem, but I want to do something on it To get input.

Problem Details:

Customers reach the domain objects almost once, 1-10 minutes (average 2 minutes) from a list, but no 2 clients ever The same object should also be used

Example Usage:

  Client X -> Some orders should be maintained in the list. WCFService :: GetNextObject () - & gt; The list of objects is basically a DB table where each object is primarily annotated, get it from DB, sort and lieutenant; - Where the X is in the next object [1, ~ 200]  

All objects with Priority 1 should be next to the next. From there the order depends on the priority level. As priority should be handed over to chronological order on a 1 object object based on a datetime, whereas priority 4 objects must be handed alphabetically depending on the string value on the object. Some point of explanation: There are other sorting schemes for different priority levels, which need to be referred to in the numerous other tables related records - this is very complex but a legitimate business case for this. is. Similarly, objects are added to this list and it is often added to potentially lot (but rarely average). [/ Edit]

I am using WCF so that any geographical location can use it through LAN / WAN and will ensure that the order has been issued and any two clients The next object is not found. Am I right in thinking that WCF is a good option for this?

One thing I wonder is the situation of the WCF service? Or, kept better: Is it stateless? Will each client's access to the service create a new logical WCF example? And if so, how is synchronization / locking normally contacted?

It should be noted that all the things here have been developed on the NIT stack, so clearly there is an existing relationship for NET Technologies. However, it is not compulsory in any way.

WCF is great for concealing details from your server - its customers - it provides a layer of abstract That would be very easy to handle the large number of customers. If some people were going to request data from the database, then I would say that WCF will be over, but it seems that it is the right use of this technique.

Regarding the status of the WCF service, it is configurable that you can run a service as a singleton, or it can create a new instance with each session or even every call Can also create.

The description of WCF examples is here (verbose!):


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -