You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by ji...@apache.org on 2004/09/16 06:41:37 UTC
[jira] Created: (DIRSEDA-4) Create an Echo ProtocolProvider in examples
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRSEDA-4
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DIRSEDA-4
Summary: Create an Echo ProtocolProvider in examples
Type: Task
Status: Open
Priority: Major
Project: Seda Framework
Assignee: Alex Karasulu
Reporter: Alex Karasulu
Created: Wed, 15 Sep 2004 9:41 PM
Updated: Wed, 15 Sep 2004 9:41 PM
Description:
We will be implementing the trivial echo protocol as defined by RFC 862 here: http://www.faqs.org/rfcs/rfc862.html.
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.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
[jira] Assigned: (DIRSEDA-4) Create an Echo ProtocolProvider in examples
Posted by ji...@apache.org.
Message:
The following issue has been re-assigned.
Assignee: Trustin Lee (mailto:trustin@gmail.com)
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRSEDA-4
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DIRSEDA-4
Summary: Create an Echo ProtocolProvider in examples
Type: Task
Status: Open
Priority: Major
Project: Seda Framework
Assignee: Trustin Lee
Reporter: Alex Karasulu
Created: Wed, 15 Sep 2004 9:41 PM
Updated: Sat, 23 Oct 2004 12:51 PM
Description:
We will be implementing the trivial echo protocol as defined by RFC 862 here: http://www.faqs.org/rfcs/rfc862.html.
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.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
[jira] Commented: (DIRSEDA-4) Create an Echo ProtocolProvider in examples
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Alex Karasulu
Created: Wed, 15 Sep 2004 10:12 PM
Body:
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:
http://issues.apache.org/jira/browse/DIRSEDA-4?page=comments#action_53125
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRSEDA-4
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
Description:
We will be implementing the trivial echo protocol as defined by RFC 862 here: http://www.faqs.org/rfcs/rfc862.html.
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.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
[jira] Commented: (DIRSEDA-4) Create an Echo ProtocolProvider in examples
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Alex Karasulu
Created: Wed, 15 Sep 2004 9:45 PM
Body:
This RFC is so darn small we might as well just plug it in here:
Network Working Group J. Postel
Request for Comments: 862 ISI
May 1983
Echo Protocol
This RFC specifies a standard for the ARPA Internet community. Hosts on
the ARPA Internet that choose to implement an Echo Protocol are expected
to adopt and implement this standard.
A very useful debugging and measurement tool is an echo service. An
echo service simply sends back to the originating source any data it
receives.
TCP Based Echo Service
One echo service is defined as a connection based application on TCP.
A server listens for TCP connections on TCP port 7. Once a
connection is established any data received is sent back. This
continues until the calling user terminates the connection.
UDP Based Echo Service
Another echo service is defined as a datagram based application on
UDP. A server listens for UDP datagrams on UDP port 7. When a
datagram is received, the data from it is sent back in an answering
datagram.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/DIRSEDA-4?page=comments#action_53122
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRSEDA-4
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 9:45 PM
Description:
We will be implementing the trivial echo protocol as defined by RFC 862 here: http://www.faqs.org/rfcs/rfc862.html.
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.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
[jira] Resolved: (DIRSEDA-4) Create an Echo ProtocolProvider in examples
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://nagoya.apache.org/jira/browse/DIRSEDA-4?page=history ]
Trustin Lee resolved DIRSEDA-4:
-------------------------------
Resolution: Fixed
It was implementes by Alex at first, and I finalized test cases. All tests including UDP passes now.
> Create an Echo ProtocolProvider in examples
> -------------------------------------------
>
> Key: DIRSEDA-4
> URL: http://nagoya.apache.org/jira/browse/DIRSEDA-4
> Project: Seda Framework
> Type: Task
> Reporter: Alex Karasulu
> Assignee: Trustin Lee
>
> We will be implementing the trivial echo protocol as defined by RFC 862 here: http://www.faqs.org/rfcs/rfc862.html.
> 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:
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