The wrapper is the mediator .

As ventilator has said all you need is a wrapper to map the managed call to the unmanaged function in acknex.dll and you are sorted. Then you can design your interface as you please around the wrapper.

I'm not too familiar with java so I can't tell you the specifics but you'll need to use J/Invoke with marshalling the types.

OK.

Do I have to synchronize all calls which are going to A8?

What do you mean by 'scynchronize'? Do you mean you will have to manually map all the functions?

i don't use java myself but i am very interested in what you will come up with. i am sure all the wrapper projects can learn a lot from each other.



in case you use SWIG, there probably would be the advantage that you could also target other SWIG supported languages (c#, lua, python,...) without too much effort. i am not very experienced with SWIG though (i used something else for my python wrapper). it could be more tricky than i think.

No.

Synchronized comes from multi-threading. If two or more threads are executing one function simultanously, the function is not synchronized. If it is synchronized, only one thread can execute it and all other threads are blocked as long as the function is terminated. Then the next one can use the code resource.

I think about cases in which several threads call the ent_create function or so. Funny stuff can then happen with the engine-internal C_LINK structure :-)

Yeah! I am just thinking about it (again, I have to admit), because I am studying intensively multi-threading concepts and implementations in Java, remote invocation calls and such stuff. Motivated by the talk in the C++ thread (atm) and re-discovering the Java is so cool and elegant through actually programming things in eclipse (my thoughts, dont fire me for that, all you C++ patriots ) I thought "is it possible to glue to these two cool things together?".

When I finished my programming homeworks in about a week, I will look into it (mainly engine invocation first... this have to work, otherwise I have to take the other way round which looks more complicated).

What I fear is to sync the engine with the Java garbage collector maybe I have to rely on the dispose pattern... and I know that you HATE patterns!

i don't dislike java. i just think there are nicer languages. c++ on the other hand is the most horrible language of them all.



i have no clue about multithreading. never looked into it. i am not sure if the engine functions are suited to be used in a multithreaded way at all?

handling garbage collection shouldn't be a big problem. it didn't seem to be one in the python and c# wrappers either.

lets just do simple steps! :-) I tell you when I got something....