I'd like to keep the restriction *for now* and continue to have publish and
access service code enforce that it won't run on a gateway.
The UK folks are setting up their own node. I've spent a little time
talking to them about the LR network model.
They are gathering input from their community about what they want to do.
If they decide to run their own network and gateway, I want to use their
input to do any revisions to the LR network model. That way we're driving
changes based on real use and needs.
If there's anyone else who wants to run their own network or community, we
would like to get their input too! Please discuss
- Dan
On Fri, Jan 20, 2012 at 2:21 PM, Suliman, Suraiya H <
suraiya.h.suli
...@lmco.com> wrote:
> Dan,
> Gateway nodes currently do not support data access or publish APIs. Do we
> want to maintain these restrictions on a Gateway node? This forces a closed
> network to consist of at least 2 nodes to be able to distribute across
> networks. This issue is outlined in
> https://www.pivotaltracker.com/story/show/12360577
> -Suraiya
--
Daniel R. Rehak, Ph.D.
Learning Registry Technical Architect
ADL Technical Advisor
Skype: drrehak
Email: daniel.re...@learningregistry.org
daniel.rehak....@adlnet.gov
Twitter: @danielrehak
Web: learningregistry.org
Google Voice: +1 412 301 3040