I want to develop an Indigo service (using February 06 CTP) with some
contract to store info in SQL Server 2005.
This contract is used by clients quite frequently (average more than once
per second) and I would like to not re-open a database connection every time
the contract is used.
How to handle this ?
Instance lifetime control (how ?) or some kind of state object ? (WebService
had application state, Indigo has something similar ?)

Thanks, I will try and observe performance, probably no problem.
However, I had parts of this service working ok with December CTP, now I
just upgraded to February CTP and I get a parser error saying
"The unknown directive 'Service' is specified" (in the .svc file)
Someone knows why ?
My svc file looks somewhat like: <%@Service language=c# Debug="true"
class="SomeNamespace.SomeClassname" %>

"Steve Drake" <steve@_NOSPAMDrakey.co.uk> wrote in message
news:8C1A459B-1418-4711-AD93-8C6DBD25298E@microsoft.com...
> ADO.NET will 'pool' the connection.
>
> If you go with a statefull connection, then how would you manage 25
> requests at the same time?
>
> Let IIS / ADO.NET manage all this for you IIS will make sure that
> requests get quied ( I think it will process 25 per CPU) and ADO.NET will
> pool the connection. I am not sure how self host console apps do, does WCF
> queue them?
>
> Just make sure you close the connection as soon as you can, this gives it
> back to the pool.
>
> I have had to test this sort of stuff before, we have used app stress
> center, we got very good results and looking at the perf results in more
> detail, Connection.Open was never an issue.
>
> Steve
>
> "magne" <magne@nospam.nospam> wrote in message
> news:eoGwM7rOGHA.1040@TK2MSFTNGP12.phx.gbl...
>>I want to develop an Indigo service (using February 06 CTP) with some
>>contract to store info in SQL Server 2005.
>> This contract is used by clients quite frequently (average more than once
>> per second) and I would like to not re-open a database connection every
>> time the contract is used.
>> How to handle this ?
>> Instance lifetime control (how ?) or some kind of state object ?
>> (WebService had application state, Indigo has something similar ?)
>>
>

Thanks a lot
(I just saw it at
http://blogs.msdn.com/edpinto/archiv...22/537027.aspx)

"Matevz Gacnik [MVP, RD]" <matevz.gacnik@gama-system.si> wrote in message
news:0AFCBC8D-9596-4FB2-A600-A5BAAFC7D12D@microsoft.com...
> Magne,
>
> Try using this syntax:
> <%@ServiceHost language=c# Debug="true">
> Service="SomeNamespace.SomeClassname" %>
>
> Service definition file syntax has changed in Feb 2006 CTP.
>
> Regards,
> Matevz.
>
> "magne" <magne@nospam.nospam> wrote in message
> news:OF7olFxOGHA.3864@TK2MSFTNGP10.phx.gbl...
>> Thanks, I will try and observe performance, probably no problem.
>> However, I had parts of this service working ok with December CTP, now I
>> just upgraded to February CTP and I get a parser error saying
>> "The unknown directive 'Service' is specified" (in the .svc file)
>> Someone knows why ?
>> My svc file looks somewhat like: <%@Service language=c# Debug="true"
>> class="SomeNamespace.SomeClassname" %>
>>
>> "Steve Drake" <steve@_NOSPAMDrakey.co.uk> wrote in message
>> news:8C1A459B-1418-4711-AD93-8C6DBD25298E@microsoft.com...
>>> ADO.NET will 'pool' the connection.
>>>
>>> If you go with a statefull connection, then how would you manage 25
>>> requests at the same time?
>>>
>>> Let IIS / ADO.NET manage all this for you IIS will make sure that
>>> requests get quied ( I think it will process 25 per CPU) and ADO.NET
>>> will pool the connection. I am not sure how self host console apps do,
>>> does WCF queue them?
>>>
>>> Just make sure you close the connection as soon as you can, this gives
>>> it back to the pool.
>>>
>>> I have had to test this sort of stuff before, we have used app stress
>>> center, we got very good results and looking at the perf results in more
>>> detail, Connection.Open was never an issue.
>>>
>>> Steve
>>>
>>> "magne" <magne@nospam.nospam> wrote in message
>>> news:eoGwM7rOGHA.1040@TK2MSFTNGP12.phx.gbl...
>>>>I want to develop an Indigo service (using February 06 CTP) with some
>>>>contract to store info in SQL Server 2005.
>>>> This contract is used by clients quite frequently (average more than
>>>> once per second) and I would like to not re-open a database connection
>>>> every time the contract is used.
>>>> How to handle this ?
>>>> Instance lifetime control (how ?) or some kind of state object ?
>>>> (WebService had application state, Indigo has something similar ?)
>>>>
>>>
>>
>>
>