directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (DIRSEDA-4) Create an Echo ProtocolProvider in examples
Date Thu, 16 Sep 2004 05:13:38 GMT
The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Wed, 15 Sep 2004 10:12 PM
The choices made to implement the echo protocol provider were dead on.  Namely we decided
to treat each chunk we recieved from the client stream as a request PDU.  Like a hot potato
we want this out of our hands and back out the door to the client so we're not wasting any
more buffers then we have to for the echo.

Basically there is no decode or encode taking place.  In both cases the substrate is returned
as is.  Each call to encode() or decode() triggers a callback since we treat each chunk as
a valid request and a response PDU.  This works out rather nicely with the NULL_ENCODER and
the NULL_DECODER.  It is however a waste to have to stage this just to pass the buffer along.
 Perhaps there can be a way to reroute based on protocol parameters.  This is something we
can look into while tuning the server.

So the biggest problem in this server is a potential race condition between requests which
are chunks of echo data.  Basically we must make sure delivery is in the order recieved. 
So the reponses going out the door must be pumpped out in the same order their respective
requests were recieved.  Funny I did not think this simple protocol would present issues but
it has.

View this comment:

View the issue:

Here is an overview of the issue:
        Key: DIRSEDA-4
    Summary: Create an Echo ProtocolProvider in examples
       Type: Task

     Status: In Progress
   Priority: Major

    Project: Seda Framework

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Wed, 15 Sep 2004 9:41 PM
    Updated: Wed, 15 Sep 2004 10:12 PM

We will be implementing the trivial echo protocol as defined by RFC 862 here:

The neat thing about this example is it will bring into question response synchronization
especially if we want to presume a chunk = a request as we receive data and stream it back
out.  This is an important consideration that may not have come about without using this protocol
as an example.

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