2009/3/4 Zé Flash <[email protected]>:
> I have still some issues regarding architecture, after discussing with
> some colleagues...What is the difference between using "context based
> addressing" and using a "proxy forwarder" to connect multiple devices
> (sensors), using a switch, while sharing the same standard IETF MIBs in all
> of them.
You seem to be confusing two different concepts.
Assume you have two "back-end" systems - Stephen and Maude,
with one master agent (Henry) sitting in front of them.
If Henry receives a request - how does it know who the request is meant for?
Whether this request relates to Stephen or to Maude?
"context based addressing" addresses that problem - there's a field in
the request (the context) which says "this request is about Maude" or
"this request is about Stephen".
Once Henry has decided that the request relates to Maude, what happens then?
"proxy forwarding" means that the request is actually passed on to Maude.
Maude provides the answer, and passes it back to Henry, who passes it back
to the original requestor.
Contrast that with the situation where Henry handles the request internally,
effectively answering on Maude's behalf.
So proxy forwarding is concerned with *how* to process the request,
while context-based addressing is concerned with *who* the request
relates to.
OK?
Dave
[ For "request" read "crown" throughout :-) ]
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
