Daiki Ueno commented: 
https://gitlab.com/gnutls/gnutls/-/merge_requests/1989#note_2665814689


Thank you for the update. May I suggest renaming the function to 
`gnutls_record_get_max_send_size` to be more consistent with the existing 
functions to access the limits?

Also I'm not entirely sure about your use-case, but is it important to know if 
the `record_size_limit` extension is negotiated (and the limit is not from the 
`max_fragment_length` extension)? For that purpose, I might suggest using 
`gnutls_ext_raw_parse` in the handshake hook function, rather than special 
casing it in the accessor function.

-- 
Reply to this email directly or view it on GitLab: 
https://gitlab.com/gnutls/gnutls/-/merge_requests/1989#note_2665814689
You're receiving this email because of your account on gitlab.com.


_______________________________________________
Gnutls-devel mailing list
Gnutls-devel@lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-devel
  • [gnutls-de... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities

Reply via email to