09-09-2007 09:54 PM
09-10-2007 08:52 AM
for us, multi-threading is a big topic. We are developing a client-server application, where multiple clients want to concurrently access ACIS.
We are currently encapsulating all calls to the ACIS API in a singleton which queues all calls to the API and processes them subsequently.
When is multi-threading support scheduled?
09-10-2007 09:03 AM
09-10-2007 01:12 PM
How about partially threaded as a first step? For example, one area that slows the user experience wrt dynamic modeling is facetting of data. What about Spatial internally threading calls such as api_facet_entity by faces?
09-10-2007 04:30 PM
09-10-2007 07:29 PM
1) InterOp (STEP import in particular)
3) File saving/loading
I do not know how much file saving/loading can really be sped up through threading, but it is the next area where our customers spend their time waiting. Of course, threaded faceting would also help in that area since faceting occurs immediately after file loading for us.
11-08-2007 08:46 AM
sorry that I reply only now, but I didn't check for follow-ups on my message ;-).
Clients can work on the same model concurrently and it works fine. But we haven't yet tested to modify entities, we only query models (getting Brep-structures, attributes etc.) and do tessellation. ACIS and IOP are the core of our CAD-Server which is queried by clients. The whole thing is based on CORBA (ACIS/IOP -> Wrapper -> CORBA-Server -> CORBA-Clients).
The only issue we face right now is freeing memory after all clients have finished working on a model ("close" the model).