COM servers in Delphi service applications -
this general question i'm hoping have specific info or recommendations.
i have application suite includes service application acts communications interface , data historian industrial pollution-control hardware. service contains singleton com server allow rest of suite have access hardware , data via service.
i've read stuff how svcom required make com servers work in delphi service apps. have , use svcom - claims. i'm not comfortable it, product , coding styles , expectations don't match, , makes debugging more of headache.
but real problem idea lengths svcom goes to make com server work in service app absolutely required. documentation, , of stuff comes in searches on subject, makes sound toolbox absolutely required com-server-in-service scenario. have couple of different 3rd-party libraries implementing opc servers, prosys sentrol , older production robots library (if you're not familiar opc, it's pretty-much ubiquitous data-interchange standard built on com) , both support opc com server being put in standard tservice-based apps without special handling beyond doing in afterinstall , beforeuninstall events done in stand-alone exe when run /regserver or /unregserver command-line switches, , of course using delayinitialize := true. @ least some com servers can done typical tservice-based apps without extraneous steps svcom goes through.
so question is: line between "what sorts of com servers work in tservice-based app" , "what causes need stuff svcom does" known? if so, and/or documented? if not, i'm kind of surprised - seems implementing com servers in service apps common need, i've several deep searches and, based on dearth of info i've found on subject, maybe it's not.
Comments
Post a Comment