Re: How to access one specific lowlevel object through a general highlevel interface?



Hm. You're saying something slightly contradictory: from one side, the
client "must send that data over the "most appropriate" communication
channel"; for the other, "it shouldn't be aware of their existance".

If your client needn't know about channel because, for example, the
"most appropriate" might change under its nose :) (i.e. there is a
reason for avoding shipping any knowledge about channels to the
client), the only way out is to define a bootstrap protocol (always the
same) with which you ask (a server, I presume) what is the current
strategy for selecting channels.

If it's a pure local code design matter instead, then just define a
SelectionStrategy object (probably a singleton, unless the strategy
depends on the context) which "knows" about how to select the best
channel out of a set of protocols, and delegate for example the choice
to the protocol itself.

.



Relevant Pages

  • [RFC PATCH 2/2] dmaengine: move channel management to the client
    ... to a specific client. ... a channel at dma_event_callback time. ... struct dma_device *device; ... * When the number of DMA channel in the system changes, ...
    (Linux-Kernel)
  • RE: Problems with security requirements in Windows WorkGroups.
    ... "A remote side security requirement was not fulfilled during authentication. ... small chat application between a client and a server ... When I try to use the TCP channel I get the error (with NO inner exception ...
    (microsoft.public.dotnet.languages.csharp)
  • [md-accel PATCH 02/19] dmaengine: make clients responsible for managing channels
    ... The current implementation assumes that a channel will only be used by one ... Instead of tracking how many channels a client wants and how many it has ... struct dma_device *device; ... * When the number of DMA channel in the system changes, ...
    (Linux-Kernel)
  • Re: .Net Remoting TCP or HTTP?
    ... John's given a good description of why you would pick either the TCP or HTTP ... The reason is that, when the server needs to notify the client of the event, ... In the TCP case, this means using a bi-directional channel, so that requests ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: .Net Remoting TCP or HTTP?
    ... John's given a good description of why you would pick either the TCP or HTTP ... The reason is that, when the server needs to notify the client of the event, ... In the TCP case, this means using a bi-directional channel, so that requests ...
    (microsoft.public.dotnet.framework)