eConnect service

Interesting question.  It does appear to be multi-threaded.

Here is the install admin guide:

http://download.microsoft.com/download/7/B/C/7BC94465-8307-4184-8D8D-E7DB8C5FF8EC/eConnectInstallAdminGuide.pdf

Section 5 notes a configuration option to specify the number of threads available, from 1 to 20 (config value of 0 to 19).

<add key="eConnect.Threads" value="0" />

I've developed integrations that have imported millions of transactions and I've never really needed multiple threads, but if you know that you will have multiple imports running simultaneously, it is probably worth adding a few threads,

One note--before turning on multiple threads, make sure to read the cautionary note on page 34:

There are scenarios where increasing the number of threads degrades system performance. If the server cannot support more threads, or custom code added to an eConnect pre or post stored procedures is not thread safe, adding threads may cause unexpected results. Changes to this key’s value require careful evaluation and testing.

So unless you have a very specific reason why you need multiple threads, and are sure that you don't have any custom code that will cause problems with multiple threads, I would stick to the default single thread.

Steve, I would like to refer another question to you on GP  Web service  on updating  the ItemRcd.  I will put this question out tomorrow..  The question is - can we to the Gp Web Service to Update the ItemRcd? We are trying staying strictly with using the Web GP Service for update and Creating an ItemRcd. If not what do you suggest?

I will place this question by tomorrow morning.

BTW - is GP Web Service multithreaded?