[ 
https://issues.apache.org/jira/browse/DIRMINA-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157393#comment-17157393
 ] 

Alexander B commented on DIRMINA-1128:
--------------------------------------

Ok, maybe i have to give some more information: We already have the 
TCP-Connection: Our application connects to a listening socket (from an 
external application), receives data, manipulate it and offers this to a new 
socket. So for this "pipeline" we consume via a SocketConnector and offers the 
new data via a SocketAcceptor (see picture).


Now, we want to implement the same way, but just based on UDP connection. For 
me it was obvious to change the SocketConnector to a DatagramConnector (on the 
left side of our application) and offers this data on a new Acceptor (on the 
right side).

Is your answer still correct to use an acceptor on our left side as well?


!tcp.png|width=236,height=104!

> UDPConnector does not receive anything
> --------------------------------------
>
>                 Key: DIRMINA-1128
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1128
>             Project: MINA
>          Issue Type: Wish
>          Components: Example
>    Affects Versions: 2.0.21
>            Reporter: Alexander B
>            Priority: Major
>         Attachments: tcp.png
>
>
> Hello guys,
>  
> I have created a simple UDP-Connector, which i reported [ here | 
> [https://stackoverflow.com/questions/62875586/mina-usage-of-datagramconnector-does-not-work]
>  ]
>  
> Can you tell me the difference between using the SocketConnector and 
> DatagramConnector and why the SocketConnector works fine, but the 
> DatagramConnector does not?
>  
> I expect, that there should be the same behaviour ... (except of the class 
> itself)
>  
> Thanks a lot
> Alex



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to