[jboss-jira] [JBoss JIRA] Commented: (JGRP-911) STREAMING_STATE_TRANSFER: investigate use of UDP datagrams instead of TCP socket

Vladimir Blagojevic (JIRA) jira-events at lists.jboss.org
Thu Mar 19 15:44:22 EDT 2009


    [ https://jira.jboss.org/jira/browse/JGRP-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458245#action_12458245 ] 

Vladimir Blagojevic commented on JGRP-911:
------------------------------------------

Yes, this new streaming state transfer should be transport independent. We can wrap output stream we provide to client app with BufferedOutputStream of a specified buffer size (say 8192). In our implementation of OutputStream we will thus always generate jgroups message that are of that certain size. In our implementation of InputStream that is provided to client app we do not need BufferedInputStream (I think). In this new streaming state transfer protocol we will queue state transfer messages as they arrive and fetch bytes from actual underlying messages and pass them to read methods of InputStream. We can use queue blocking mechanism to block InputStream read methods until jgroups message carrying state transfer arrive. 

> STREAMING_STATE_TRANSFER: investigate use of UDP datagrams instead of TCP socket
> --------------------------------------------------------------------------------
>
>                 Key: JGRP-911
>                 URL: https://jira.jboss.org/jira/browse/JGRP-911
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Vladimir Blagojevic
>             Fix For: 2.6.9, 2.8
>
>
> We currently use TCP server and client sockets to transfer state with STREAMING_STATE_TRANSFER. Add an option to use the default transport (could be TCP, could be UDP).
> State provider:
> - Write state into an output stream
> - The output stream generates unicast messages of a fixed size and sends them to the state receiver 
> State receiver:
> - Provides an input stream
> - The app reads data off of that stream
> - The received message chunks are placed into the input stream
> Might be more firewall friendly and causes less config overhead (e.g. punching of holes for the TCP conn in the FW).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list