directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (DIR-5) Generic frontend plumbing
Date Fri, 05 Mar 2004 04:24:31 GMT
The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Thu, 4 Mar 2004 8:23 PM
       Body:
Got the input manager working solid and handling any NIO idiosynchracies.  Even got to a point
where a simple client is generating messages and the server is capturing it.  Yeah this is
no big deal at all but its the seed to more to come.

---------------------------------------------------------------------
View this comment:
  http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=DIR-5&page=comments#action_20977

---------------------------------------------------------------------
View the issue:
  http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=DIR-5

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIR-5
    Summary: Generic frontend plumbing
       Type: Task

     Status: In Progress
   Priority: Major

    Project: Directory
 Components: 
             Eve

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Sun, 15 Feb 2004 10:48 PM
    Updated: Thu, 4 Mar 2004 8:23 PM

Description:
I need to test the frontend plumbing before messing around with all the asn.1 stuff and backend
integration.  I can simulate the same dynamics of dealing with messages usign a stateful protocol
in a SEDA server using bogus messages.

If I create a simple harness I can also guage performance as well as sort out any issues having
to do with NIO implementations.  

Other components within the system can then be added.  The use of
the event bus/router makes it really easy now to snap in new event driven components as well
as stages by subscribing them for reciept of events by type.

What I'm looking at here is to verify the network plubing and add supporting structures around
the networking code before getting LDAP specific.  This includes session tracking, and request
tracking.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message