<adrian.vladimirov@gmail.com> wrote in message
news:e033137c-d80a-4c6e-b5fc-485169e09fd5@d77g2000hsb.googlegroups.com...
> so thats what I have :
> a web service, lets say is called "Facility" and it`s primary goal is
> to submit some information to the database.
> the problem comes, when from another service/app (consumer) I send
> such information to the Facility service..
> all works fine, but in the end the "consumer" wants to make an report
> (select) from the database , to recieve what has been saved (report).
>
> of course the problem is the concurrence between the services.. while
> the calling one is done with all the async seding to the Facility
> service, it makes request to build the report. But meanwhile NOT all
> of the data has been submitted to the databasa, due to traffic/sql
> server concurrency and so forth..
>
> the easiest workaround is to force a waiting time before requesting
> the report, but I think you can offer a smarter approach when no time
> is wasted on sleep mode ..
>
> the "Facility" service is builded on .net 3.5 WCF , hosted by ASP.NET
> IIS6 with the conditions :
>
> [ServiceBehavior(InstanceContextMode = InstanceContextMode.Single,
> ConcurrencyMode = ConcurrencyMode.Multiple,
> IncludeExceptionDetailInFaults = true)]
>
> I tried a solution with an EXTRA call to the service, to explicitly
> check if all the data has been submited, but this way the extra call
> can EVEN happen before the service has recieved all the previous data
> of the wire ..
>
> thanks in advance for any ideas :)

wrote:

>so thats what I have :
>a web service, lets say is called "Facility" and it`s primary goal is
>to submit some information to the database.
>the problem comes, when from another service/app (consumer) I send
>such information to the Facility service..
>all works fine, but in the end the "consumer" wants to make an report
>(select) from the database , to recieve what has been saved (report).
>
>of course the problem is the concurrence between the services.. while
>the calling one is done with all the async seding to the Facility
>service, it makes request to build the report. But meanwhile NOT all
>of the data has been submitted to the databasa, due to traffic/sql
>server concurrency and so forth..
>
This sounds like an ill-behaved client.
>the easiest workaround is to force a waiting time before requesting
>the report, but I think you can offer a smarter approach when no time
>is wasted on sleep mode ..
>