Navigation


Changeset 1014:908ffbb81f60 in freeDiameter for libfdcore/routing_dispatch.c


Ignore:
Timestamp:
Mar 29, 2013, 6:30:59 PM (11 years ago)
Author:
Sebastien Decugis <sdecugis@freediameter.net>
Branch:
default
Phase:
public
Message:

Added a second callback in fd_msg_send_timeout to handle more easily the timeout situation

File:
1 edited

Legend:

Unmodified
Added
Removed
  • libfdcore/routing_dispatch.c

    r974 r1014  
    467467
    468468                /* Retrieve any registered handler */
    469                 CHECK_FCT( fd_msg_anscb_get( qry, &anscb, &data ) );
     469                CHECK_FCT( fd_msg_anscb_get( qry, &anscb, NULL, &data ) );
    470470
    471471                /* If a callback was registered, pass the message to it */
     
    793793        struct rtd_candidate * c;
    794794        struct msg *msgptr = msg;
     795        DiamId_t qry_src = NULL;
     796        size_t qry_src_len = 0;
    795797       
    796798        /* Read the message header */
     
    801803        if ( ! is_req ) {
    802804                struct msg * qry;
    803                 DiamId_t qry_src = NULL;
    804                 size_t qry_src_len = 0;
    805805                struct msg_hdr * qry_hdr;
    806806                struct fd_peer * peer = NULL;
     
    832832       
    833833        /* From that point, the message is a request */
     834        CHECK_FCT( fd_msg_source_get( msgptr, &qry_src, &qry_src_len ) );
     835        /* if qry_src != NULL, this message is relayed, otherwise it is locally issued */
    834836
    835837        /* Get the routing data out of the message if any (in case of re-transmit) */
Note: See TracChangeset for help on using the changeset viewer.