Olivier Beytrison wrote: > Hello Benny, > > Thank you very much for your welcome. > > As for your answers, I've already contacted Sasa off-list and got also a > quick answer from her. There might be another possibility, the one to > use the client/server model. Having the core function built in C++ and > listening to the GUI (the client) on a local port might make it safer > and more flexible. Somehow I doubt this. If any, we're just reinventing ActiveX here! > And don't forget that the target of this open-source application is a > mobile device running Windows Mobile 5 or 6, with its compact framework > .Net. Would that make any difference in the wrapper? Another option is to build PJSUA-LIB as (unmanaged) DLL. We already have the framework for exporting symbols in PJSIP (because it's needed by Symbian S60, and that's what PJ_DECL()/PJ_DEF() are for!) so creating a DLL might not be that hard. What I'm not sure is whether it would be easy to access this DLL from .NET, considering that data types (struct's) declarations are not exported by DLLs. > If we stay on the wrapper idea, we will indeed develop a sort of > "intermediate" API which will provide only what is strictly needed by > the GUI part of the application, this preventing us to wrap over 100 > functions and callbacks. The problem with that is of course different people will need different APIs, so this might limit the reusability of the wrapper. ;-) Comments anyone? cheers, -benny > Anyway, I'll keep the list informed on which way the project will take, > and will be happy to listen to anyone's suggestion or ideas :) > > Regards, > Olivier B.
