directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Assigned: (DIRSEDA-17) Should the ClientKey expose the socket? Don't think so.
Date Sat, 23 Oct 2004 19:51:29 GMT

   The following issue has been re-assigned.

   Assignee: Trustin Lee (
View the issue:

Here is an overview of the issue:
        Key: DIRSEDA-17
    Summary: Should the ClientKey expose the socket? Don't think so.
       Type: Improvement

     Status: Open
   Priority: Major

    Project: Seda Framework

   Assignee: Trustin Lee
   Reporter: Alex Karasulu

    Created: Sun, 21 Mar 2004 7:54 AM
    Updated: Sat, 23 Oct 2004 12:50 PM

Revisit whether or not the ClientKey should expose the client's socket connection.  I think
this is totally unsafe and decided to go with it for ease instead of taking the right precautions.
 Let's refactor this so only the events carry what they need like the channel rather than
carrying and exposing the needed handles in the key.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message