Note that there are some explanatory texts on larger screens.

plurals
  1. USbjhuffine
    primarykey
    data
    text
    plurals
    1. COI don't have a choice. One of the two applications is a third-party exe that I have no control over. I can, however, develop a dll that the third-party application is capable of loading. The WCF service allows me to control and manage the third-party application (and the files it manages) from another, external application, thus the application "pair" (a dll loaded in a third-party app and a client exe). I'll update the question for clarity, but didn't put it in there at first because I was afraid to confuse the question.
      singulars
    2. COBtw... I really appreciate your insight. Being new to WCF, it's just as easy to question best practices as it is how it works. Out of curiousity though, is it possible to self-host a separate instance of the service using a more dynamic endpoint address that only the application "pair" would know? That would allow it to be stateless, whereas just as you explained it is stateful so that it can track who's communicating with whom.
      singulars
    3. COOkay, that's how it's designed now. I basically created a unique, but generic, ID object that uses a Guid to generate the actual ID value. Then I have the one service application and server application. This morning I was taking a fresh look at its design and got to wondering if maybe what I was doing would be better by self-hosting in one of the client apps with a unique endpoint address per application "pair". The thought was maybe that would reduce the need of using an ID, but I wasn't sure if this was even possible or practiced. Sounds like I just need to stick with what I have.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload