Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: pass (nike.apache.org: domain of bishnu35@hotmail.com designates
 65.55.90.146 as permitted sender)
Message-ID: <SNT145-W679274F6D647FE67E1278C2AA0@phx.gbl>
Content-Type: multipart/alternative;
	boundary="_317ff217-32c2-44e5-b0d9-ccc05bba0591_"
From: Bishnu Gautam <bishnu35@hotmail.com>
To: <dev@river.apache.org>
Subject: RE: WELCOME to dev@river.apache.org
Date: Tue, 4 Sep 2012 00:26:32 +0000
Importance: Normal
In-Reply-To: <50446687.1010303@zeus.net.au>
References: <1346546925.76176.ezmlm@river.apache.org>
 <SNT145-W1432C0EB0041A269D65527C2A40@phx.gbl>,<50446687.1010303@zeus.net.au>
MIME-Version: 1.0

--_317ff217-32c2-44e5-b0d9-ccc05bba0591_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi Peter and Simon
Thanks for messages.Yes=2C I was thinking of DNS-SRV discovery. Also=2C UDT=
 is better than TCP. I am very interested to use Java UDT and totally agree=
 to apply this protocol. That will efficiently work I think. I am building =
an application that transfer all bundled JPanel wraped jini/river services =
to client sides. I am able to execute it in muliti-Lan environment. I will =
donate this code to river community. My next phase is to implement it to ex=
ecute in internet. If you guys have already implemented some of it=2C lets =
share the codes or lets discuss so that we can bring river project as one o=
f the demanding solution not only in distributed environment but also for t=
he cloud community. I think this is the right time for jini/river community=
 to come into the business or into the cloud.
RegardsBishnu


Bishnu Prasad Gautam


> Date: Mon=2C 3 Sep 2012 18:12:55 +1000
> From: jini@zeus.net.au
> To: dev@river.apache.org
> Subject: Re: WELCOME to dev@river.apache.org
>=20
> Thanks Bishnu=2C welcome to River!
>=20
> I've had some plans with regard to internet based services=2C not much=20
> implemented I'm afraid=2C time constraints...
>=20
>    1. org.apache.river.api.lookup.StreamServiceRegistrar - interface for
>       internet based service registrars (lookup service).
>    2. DNS-SRV Discovery=2C to use in place of multicast discovery=2C this
>       (not yet implemented) discovers the location of lookup services=2C
>       to be used in Unicast Discovery.
>    3. Java UDT Sockets - not yet implemented=2C this is basically Data
>       over UDP=2C which is easier to get through firewalls than TCP.
>=20
> Regards=2C
>=20
> Peter.
>=20
> Bishnu Gautam wrote:
> > Hello River Team
> > It seems that Jini is getting its pace in terms of River. This is good =
indication and I think that River has great potential if we can build some =
application that can interact over Internet.I am planning to do a research =
work whether we can make an application of River that can interact over int=
ernet as I found there are some issues of firewall etc. Would you let me kn=
ow=2C whether the River team has plan of bringing River on the Internet ?=20
> >
> > Bishnu Prasad Gautam=20
> >
> >  =20
> >> Date: Sun=2C 2 Sep 2012 00:48:45 +0000
> >> From: dev-help@river.apache.org
> >> To: bishnu35@hotmail.com
> >> Subject: WELCOME to dev@river.apache.org
> >>
> >> Hi! This is the ezmlm program. I'm managing the
> >> dev@river.apache.org mailing list.
> >>
> >> I'm working for my owner=2C who can be reached
> >> at dev-owner@river.apache.org.
> >>
> >> Acknowledgment: I have added the address
> >>
> >>    bishnu35@hotmail.com
> >>
> >> to the dev mailing list.
> >>
> >> Welcome to dev@river.apache.org!
> >>
> >> Please save this message so that you know the address you are
> >> subscribed under=2C in case you later want to unsubscribe or change yo=
ur
> >> subscription address.
> >>
> >>
> >> --- Administrative commands for the dev list ---
> >>
> >> I can handle administrative requests automatically. Please
> >> do not send them to the list address! Instead=2C send
> >> your message to the correct command address:
> >>
> >> To subscribe to the list=2C send a message to:
> >>    <dev-subscribe@river.apache.org>
> >>
> >> To remove your address from the list=2C send a message to:
> >>    <dev-unsubscribe@river.apache.org>
> >>
> >> Send mail to the following for info and FAQ for this list:
> >>    <dev-info@river.apache.org>
> >>    <dev-faq@river.apache.org>
> >>
> >> Similar addresses exist for the digest list:
> >>    <dev-digest-subscribe@river.apache.org>
> >>    <dev-digest-unsubscribe@river.apache.org>
> >>
> >> To get messages 123 through 145 (a maximum of 100 per request)=2C mail=
:
> >>    <dev-get.123_145@river.apache.org>
> >>
> >> To get an index with subject and author for messages 123-456 =2C mail:
> >>    <dev-index.123_456@river.apache.org>
> >>
> >> They are always returned as sets of 100=2C max 2000 per request=2C
> >> so you'll actually get 100-499.
> >>
> >> To receive all messages with the same subject as message 12345=2C
> >> send a short message to:
> >>    <dev-thread.12345@river.apache.org>
> >>
> >> The messages should contain one line or word of text to avoid being
> >> treated as sp@m=2C but I will ignore their content.
> >> Only the ADDRESS you send to is important.
> >>
> >> You can start a subscription for an alternate address=2C
> >> for example "john@host.domain"=2C just add a hyphen and your
> >> address (with '=3D' instead of '@') after the command word:
> >> <dev-subscribe-john=3Dhost.domain@river.apache.org>
> >>
> >> To stop subscription for this address=2C mail:
> >> <dev-unsubscribe-john=3Dhost.domain@river.apache.org>
> >>
> >> In both cases=2C I'll send a confirmation message to that address. Whe=
n
> >> you receive it=2C simply reply to it to complete your subscription.
> >>
> >> If despite following these instructions=2C you do not get the
> >> desired results=2C please contact my owner at
> >> dev-owner@river.apache.org. Please be patient=2C my owner is a
> >> lot slower than I am =3B-)
> >>
> >> --- Enclosed is a copy of the request I received.
> >>
> >> Return-Path: <bishnu35@hotmail.com>
> >> Received: (qmail 76169 invoked by uid 99)=3B 2 Sep 2012 00:48:45 -0000
> >> Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.=
136)
> >>     by apache.org (qpsmtpd/0.29) with ESMTP=3B Sun=2C 02 Sep 2012 00:4=
8:45 +0000
> >> X-ASF-Spam-Status: No=2C hits=3D2.4 required=3D5.0
> >> 	tests=3DFREEMAIL_ENVFROM_END_DIGIT=2CHTML_MESSAGE=2CRCVD_IN_DNSWL_NON=
E=2CSPF_PASS
> >> X-Spam-Check-By: apache.org
> >> Received-SPF: pass (athena.apache.org: domain of bishnu35@hotmail.com =
designates 65.55.90.77 as permitted sender)
> >> Received: from [65.55.90.77] (HELO snt0-omc2-s2.snt0.hotmail.com) (65.=
55.90.77)
> >>     by apache.org (qpsmtpd/0.29) with ESMTP=3B Sun=2C 02 Sep 2012 00:4=
8:36 +0000
> >> Received: from SNT145-W136 ([65.55.90.71]) by snt0-omc2-s2.snt0.hotmai=
l.com with Microsoft SMTPSVC(6.0.3790.4675)=3B
> >> 	 Sat=2C 1 Sep 2012 17:48:15 -0700
> >> Message-ID: <SNT145-W136CD0261B4D1C6B55983A4C2A40@phx.gbl>
> >> Content-Type: multipart/alternative=3B
> >> 	boundary=3D"_8d4cc292-55ff-42a6-92f3-b39be91ffb52_"
> >> X-Originating-IP: [122.18.73.194]
> >> From: Bishnu Gautam <bishnu35@hotmail.com>
> >> To:
> >> 	<dev-sc.1346546661.bpbohbfainpplmmplpaj-bishnu35=3Dhotmail.com@river.=
apache.org>
> >> Subject: RE: confirm subscribe to dev@river.apache.org
> >> Date: Sun=2C 2 Sep 2012 00:48:15 +0000
> >> Importance: Normal
> >> In-Reply-To: <1346546661.69982.ezmlm@river.apache.org>
> >> References: <1346546661.69982.ezmlm@river.apache.org>
> >> MIME-Version: 1.0
> >> X-OriginalArrivalTime: 02 Sep 2012 00:48:15.0984 (UTC) FILETIME=3D[A35=
45700:01CD88A4]
> >> X-Virus-Checked: Checked by ClamAV on apache.org
> >>
> >>    =20
> >  		 	   		 =20
> >  =20
>=20
 		 	   		  =

--_317ff217-32c2-44e5-b0d9-ccc05bba0591_--