]
Andrew Oliver closed JBMAIL-46.
-------------------------------
Resolution: Won't Fix
Assignee: (was: Andrew Oliver)
POP Client Proxy
----------------
Key: JBMAIL-46
URL:
http://jira.jboss.com/jira/browse/JBMAIL-46
Project: JBoss Mail ** Closed - moved to
http://buni.org **
Issue Type: Sub-task
Reporter: Andrew Oliver
Original Estimate: 1 day
Remaining Estimate: 1 day
The POP client proxy mimic's a real POP Server however it translates the requests
into the HTTP requests expected by:
http://jira.jboss.com/jira/browse/JBMAIL-42
Expectations:
1. It issues the
http://servername/POP/CONNECT on initial connection from the client and
returns the greeting from HTTP Pop proxy which in turn is just returning the real
server's greeting. From then on the jsessionid is associated with THIS connection to
the client.
2. It hangs up on the client if it gets an invalid session from the server (avoid having
to smartly implement the protocols to reconnect to a return to state and leave it up to
the client to do that).
3. Server proxy is "locked down" to connect to only one host or set of hosts
(so you can't use this to launch a distributed denial of service attack against a
third party, sorry)
Possiblities:
1. Could be a protocol implementation for JBoss Mail's framework that simply uses
something like Jakarta Commons HTTPClient to issue commands to the server proxy. Thus you
run parts of JBoss AS and JBMailServer on client and server.
2. This could be dumbly implemented to support ANY protocol if some standardization on
the SERVER Proxy and Client Proxy can be thought of.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: