> On Dec 14, 2015, at 5:23 PM, Robin Sommer <[email protected]> wrote: > > Broker generates these two events in Bro: > > event BrokerComm::outgoing_connection_established(peer_address: string, > peer_port: port, > peer_name: string) > > event BrokerComm::incoming_connection_established(peer_name: string) > > I was just trying to see if I could add the address and port arguments > to the incoming event as well, so that one knows where the connection > is coming from.
Don’t think that info is available in Broker due to CAF abstracting it away. Don’t remember at the moment how that info can be extracted from CAF. Maybe there’s even a simple function to get addr/port of a remote actor, but I also recall lower level networking stuff might be available from within the “broker” class in CAF. If the later is the recommended way to go, there’d need to be some code factoring in Broker to actually use that “broker” system of CAF. - Jon _______________________________________________ bro-dev mailing list [email protected] http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
