Results 1 to 7 of 7

Thread: Inter-process communication

  1. #1

    Thread Starter
    New Member
    Join Date
    Apr 2003
    Location
    NZ
    Posts
    10

    Inter-process communication

    Hi

    I have to build an application with a comms backend, all using .net

    The requirement is that the communication code is obviously run in a seperate thread, in this case i would like to run it as a windows service.

    Now i need to be able to communicate with that service from a windows forms application, and at first it seems that MSMQ would be the thing to use for that..

    Now the interesting thing is that this might be needed to run within the compact framework at some point as well, and im not sure if windows services or MSMQ is included in the compact framework.

    Can anybody clarify things here for me?
    thanks

  2. #2
    Junior Member
    Join Date
    Apr 2003
    Posts
    18
    my thought would be, if you are going to write it as a service anyway and you want to have access from a wide range of clients "compact framework", etc. Why not write the service as a web service and use XML as your inter-process com method.
    www.WinMgmt.com
    [email protected]

  3. #3

    Thread Starter
    New Member
    Join Date
    Apr 2003
    Location
    NZ
    Posts
    10
    No can do, the backend needs to be able to run on the compact framework device as well... see im not sure if a 'windows service' per se will run on the compact framework...

    ... and then also if MSMQ will also work there too.

    Compact framework aside, does using a service and msmq sound like a reasonable solution?

    as for the web service idea, we aren't looking for that kind of distribution.. Im seeing the client mostly being run on the same machine as the service, and certainly not available as a web service.

    The 'backend' software is for controlling a hardware device...
    this is not the kind of thing that really would need web type exposure.

    thanks

  4. #4
    Junior Member
    Join Date
    Apr 2003
    Posts
    18
    framework aside, does using a service and msmq sound like a reasonable solution?
    If you are running all layers on the same device I would simply process the comm part Async on a sepearate thread in its own AppDomain.
    www.WinMgmt.com
    [email protected]

  5. #5

    Thread Starter
    New Member
    Join Date
    Apr 2003
    Location
    NZ
    Posts
    10
    Then communicate via Events? or a still use a mediator class of some kind to manage communications?? or maybe MSMQ.

  6. #6
    Junior Member
    Join Date
    Apr 2003
    Posts
    18
    I would use Async Call back methods.
    www.WinMgmt.com
    [email protected]

  7. #7

    Thread Starter
    New Member
    Join Date
    Apr 2003
    Location
    NZ
    Posts
    10
    thanks for the help

    So far what ive looked at for these two topics this path seems pretty complex or maybe badly explained...

    can anybody point me at any good articles/books for this kind of architecture? particulary the remoting..

    thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width