Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. COM+ component design consideration.

COM+ component design consideration.

Scheduled Pinned Locked Moved IT & Infrastructure
questioncomdesignsysadmin
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    leonwoo
    wrote on last edited by
    #1

    Hi, I have a question regarding the COM+ design consideration. I am considering to design a COM+ host which hosts a component using containtment technique that is registered under the Component Service. However, that particular COM+ host is also registered into the Component Service. The layered view is: COM+ Host/wrapper for APP1 | | APP1 COM server object | | Component Service. My questions are: 1. What are the consideration that I need to make for such a design? 2. Do I need to consider object synchronization if the COM+ host for APP1 is in a 'Both' threading model? 3. If both the APP1 COM object and COM+ host support object pooling, what is the design consideration? Thanks.:-O leonwoo

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups