Hi Dan, below is the link to the issue.
https://issues.apache.org/jira/browse/RIVER-452
On Mon, Mar 12, 2018 at 2:27 PM, Dan Rollo wrote:
> Hi Peter,
>
> I started to try and find 'River-452’ in Jira, but can not having any luck
> finding our Jira. What am I missing?
>
>
l server removed your attachment, apache uses Jira,
> so any contributions are licensed under al2.
>
> Thanks,
>
> Peter.
>
>
> On 11/02/2018 2:44 AM, Gerard Fulton wrote:
>
>> As part of a larger effort the attached patch, jini-spec.patch, contains
>> updates th
ight be others interested in becoming involved as well.
> >
> > Thanks,
> >
> > Peter.
> >
> >> On 1/02/2018 12:09 PM, Gerard Fulton wrote:
> >> Hi Guys,
> >>
> >>
> >>
> >> I wanted to float an idea by
!
-Gerard Fulton
One potential approach is to create a service that registers a proxy that
is capable of communicating across networks.
On Wed, Jun 3, 2015 at 6:58 PM, Sergio Gomes sergio_go...@fedeltapos.com
wrote:
Hi, I have an client/server application using Apache River using the
BasicJeriExporter over
The ClassServer could be replaced with and sock web server like Apache or
Jetty to serve up classes/codebase via http.
On Tue, Jun 25, 2013 at 11:18 AM, Tom Hobbs tvho...@googlemail.com wrote:
Hi Matt,
If my memory serves me, River still has the same dependency so you should
be fine just
One easy option may be to write a simple client using your old code to
serialize the entries in the space to XML on disk. Then launch your new
application and put entries into the space instance.
On Mon, Feb 4, 2013 at 3:34 AM, Dawid Loubser da...@travellinck.com wrote:
Thanks for the quick
implemented a JavaSpace at least ;)
Seriously, if you need some advice or whatever, punt a request up
here
Dawid
On Mon, 2013-02-04 at 06:56 -0800, Gerard Fulton wrote:
One easy option may be to write a simple client using your old code to
serialize the entries
Agreed.
On Tue, Nov 13, 2012 at 6:57 PM, Gregg Wonderly ge...@cox.net wrote:
Of course, the practical matter, is that in this day and age, server port
numbers indicate specific types of services for the things in
/etc/services. But, really, we should move the whole discovery business
away
One possibility may be to consider makeing LookupLocator an interface
given that there are only two methods that really matter.
Implementations could support a socket based protocol like it is now
and other protocols in the future. I know that this would affects
current deployments; but it gives
Sounds like the tests might need to be refactored.
On Thu, Nov 1, 2012 at 4:09 AM, Peter Firmstone j...@zeus.net.au wrote:
I've noticed some new classes in the net.jini namespace, we need to move
them to org.apache.river prior to release please, unless there is a good
reason they should be
11 matches
Mail list logo