s.net.au <mailto:j...@zeus.net.au>>
> Subject: Re: River revamp
> Date: November 12, 2016 at 1:25:49 AM EST
> To: dev@river.apache.org <mailto:dev@river.apache.org>
>
>
> We could make this the basis for a new release, almost as is. I'd need to
> create some
the ocean”
syndrome where nothing can be released until it’s “all done”.
-Dan
From: Peter <j...@zeus.net.au <mailto:j...@zeus.net.au>>
Subject: Re: River revamp
Date: November 12, 2016 at 1:25:49 AM EST
To: dev@river.apache.org <mailto:dev@river.apache.org>
We could make this t
eter<j...@zeus.net.au<javascript:;>>
Sent: 06/11/2016 08:23:06 pm
To: dev@river.apache.org<javascript:;>
Subject: Re: River revamp
Yes same pattern, some details are different for security reasons,
additional support is required for lower level protocols as object
endpoints.
Also, f
le...
Thoughts / suggestions?
Regards,
Peter.
Sent from my Samsung device.
Include original message
Original message
From: Peter<j...@zeus.net.au>
Sent: 06/11/2016 08:23:06 pm
To: dev@river.apache.org
Subject: Re: River revamp
Yes same pattern, some details are different for securit
nt version of
>>>>> River
>>>>> trunk.
>>>>> * We want to change to using a git repo for River.
>>>>> * Start building maven style modules from the ground up, starting with
>>>>> JERI at low level.
>>>>&g
--- Original message
From: Peter<j...@zeus.net.au>
Sent: 06/11/2016 08:23:06 pm
To: dev@river.apache.org
Subject: Re: River revamp
Yes same pattern, some details are different for security reasons,
additional support is required for lower level protocols as object
endpoints.
Also, f
le...
>
> Thoughts / suggestions?
>
> Regards,
>
> Peter.
>
> Sent from my Samsung device.
>
> Include original message
> Original message
> From: Peter <j...@zeus.net.au <javascript:;>>
> Sent: 06/11/2016 08:23:06 pm
> To: dev@river.apa
?
* junit tests with appropriate module...
Thoughts / suggestions?
Regards,
Peter.
Sent from my Samsung device.
Include original message
Original message
From: Peter<j...@zeus.net.au>
Sent: 06/11/2016 08:23:06 pm
To: dev@river.apache.org
Subject: Re: River revamp
Yes same pat
ng device.
>>
>> Include original message
>> Original message
>> From: Peter <j...@zeus.net.au>
>> Sent: 06/11/2016 08:23:06 pm
>> To: dev@river.apache.org
>> Subject: Re: River revamp
>>
>> Yes same pattern, some details are different f
06/11/2016 08:23:06 pm
To: dev@river.apache.org
Subject: Re: River revamp
Yes same pattern, some details are different for security reasons,
additional support is required for lower level protocols as object
endpoints.
Also, for example, devices were on a 6LowPAN network, different types of
devices
module...
Thoughts / suggestions?
Regards,
Peter.
Sent from my Samsung device.
Include original message
Original message
From: Peter <j...@zeus.net.au>
Sent: 06/11/2016 08:23:06 pm
To: dev@river.apache.org
Subject: Re: River revamp
Yes same pattern, some details are dif
he utility service when a
device is down.
Regards,
Peter.
Sent from my Samsung device.
Include original message
Original message ----
From: Zsolt Kúti<la.ti...@gmail.com>
Sent: 03/11/2016 05:37:45 pm
To: dev@river.apache.org
Subject: Re: River revamp
A small footprint implementation of Jini'
d constrained devices with a lookup service and manages it's
>>>> lease. This utility can generate attributes (from Configuration) and
>>>> provide a bootstrap proxy (service) to allow clients to authenticate and
>>>> obtain the smart proxy used to communicate
age
Original message
From: Zsolt Kúti<la.ti...@gmail.com>
Sent: 03/11/2016 05:37:45 pm
To: dev@river.apache.org
Subject: Re: River revamp
A small footprint implementation of Jini's lookup service written in C,
fully JCK compliant.
http://www.psinaptic.com/link_files/PsiNapticTe
) to allow clients to authenticate and
>>> obtain the smart proxy used to communicate directly with the device.
>>>
>>> * Provide an interface for clients to notify the utility service when a
>>> device is down.
>>>
>>> Regards,
>>>
to notify the utility service when a
device is down.
Regards,
Peter.
Sent from my Samsung device.
Include original message
Original message
From: Zsolt Kúti<la.ti...@gmail.com>
Sent: 03/11/2016 05:37:45 pm
To: dev@river.apache.org
Subject: Re: River revamp
A small footprint
from my Samsung device.
>
> Include original message
> Original message
> From: Zsolt Kúti <la.ti...@gmail.com>
> Sent: 03/11/2016 05:37:45 pm
> To: dev@river.apache.org
> Subject: Re: River revamp
>
> A small footprint implementation of Jini's lookup service
message
From: Zsolt Kúti <la.ti...@gmail.com>
Sent: 03/11/2016 05:37:45 pm
To: dev@river.apache.org
Subject: Re: River revamp
A small footprint implementation of Jini's lookup service written in C,
fully JCK compliant.
http://www.psinaptic.com/link_files/PsiNapticTelematics.pdf
A few yea
Https://www.reddit.com/r/IOT
Might provide some hints.
Sent from my Samsung device.
Include original message
Original message
From: Patricia Shanahan <p...@acm.org>
Sent: 03/11/2016 12:41:54 am
To: dev@river.apache.org
Subject: Re: River revamp
I think for this t
Sent from my Samsung device.
Include original message
Original message
From: Patricia Shanahan <p...@acm.org>
Sent: 03/11/2016 12:41:54 am
To: dev@river.apache.org
Subject: Re: River revamp
I think for this to work it is necessary to find out where IoT people
ha
Will respond with more soon
>
> Regards,
>
> Peter.
>
> Sent from my Samsung device.
>
> Include original message
> Original message
> From: Niclas Hedhman <nic...@hedhman.org>
> Sent: 03/11/2016 12:39:33 pm
> To: dev@river.apache.org
> Subject: Re
.
Include original message
Original message
From: Niclas Hedhman <nic...@hedhman.org>
Sent: 03/11/2016 12:39:33 pm
To: dev@river.apache.org
Subject: Re: River revamp
"IoT" is a term that for this discussion is a bit too wide. The
"thermostat" runs with
gt; It's not going to step on any Jini discovery lookup stuff and it's going
>>> to be easily deployed by new users.
>>>
>>> Then once users realise there's more on offer they can take advantage as
>>> their understanding develops.
>>>
>>> Cheers,
>>
From: Niclas Hedhman <nic...@hedhman.org>
Sent: 02/11/2016 05:31:26 pm
To: dev@river.apache.org
Subject: Re: River revamp
To put a bit more meat on Peter's condensed list...
I put forward a proposal to sever the ties between River and Jini itself,
and instead re-focus
To put a bit more meat on Peter's condensed list...
I put forward a proposal to sever the ties between River and Jini itself,
and instead re-focus River to be a a secured network transport, with
optional discovery. Starting point is of course the JERI module and Peter's
work to secure this
A discussion recently ignited on river private about revamping the project.
For the benefit of the wider developer community can we restate the suggestions
here, feel free to reword, correct, reject or suggest. It was along the lines
of:
* Website revamp
* Remove Jini focus, with a historical
26 matches
Mail list logo
