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
Workspace z/OS Connect
Created by Guest
Created on May 14, 2020

zCEE: Support for WebSocket Clients

We have a requirement to establish WebSocket connection with our partner application to receive the various responses since the partner application supports only WebSocket API connection while sending its responses.

Idea priority Medium
  • Guest
    Reply
    |
    Nov 2, 2020

    Thank you for this RFE.

    Unfortunately there was not enough information to allow us to effectively assess this requirement. In a previous comment we requested the information that would help us clarify key points, but this information has not been provided.

    Regreably this means that we cannot effectively assess this requirement and so our only option is to declined it at this point. You are free to re-raise this requirement with the detail requested if you still want it to be considered.

  • Guest
    Reply
    |
    Aug 5, 2020

    Thank you for the RFE.

    It is not clear from the description whether your use case is concerning API provider or API requester (or maybe it is both?). If you could clarify that would be helpful.

    Also, we would like to understand how you envisage the concepts of HTTP based REST API calls and WebSockets working together?
    - What advantages does this bring?
    - What can be achieved with WebSockets that cannot be achieved with HTTP?
    - Do you have an example of a REST API that uses WebSockets?

  • Guest
    Reply
    |
    May 14, 2020

    Added functionality would be a needed improvement.