Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories z/TPF
Created by Guest
Created on Nov 14, 2017

Allow for sub-second SSL_write when using Shared CTX

Since Shared CTX SSL_write() is always blocking from an application perspective, we must rely on the socket send timeout (SO_SNDTIMEO) to get control back should an event occur such as insufficient send buffer space. SO_SNDTIMEO is only granular to the second. This is much to long to wait for time-critical applications.

Idea priority High
  • Guest
    Reply
    |
    Dec 12, 2017

    IBM does not intend to implement this in the foreseeable future.
    Implementing subsecond send/recv timeouts in SSL is a fairly large effort due to the underlying second based timeouts in the TCP/IP layer. With the true non-blocking SSL_write's (developerWorks RFE ID 113047), subsecond timeouts on SSL_write can be accomplished in the application as they would now properly get control back with a WANT_WRITE return code if the socket was blocked.