Hi, I think it makes sense as JSON has become a widely adopted standard. We should certainly wait for 4.1 though. At first, I thought you were talking about the Unicon extension : https://github.com/Unicon/cas-addons/wiki/Configuring%20JSON%20Service%20Registry . It seems to be the same idea, isn't it. Best regards, Jérôme
2013/10/8 Marvin S. Addison <[email protected]> > I'm curious whether there's any interest in contributing our JSON service > registry to the official CAS project. > > https://gist.github.com/serac/**6886509<https://gist.github.com/serac/6886509> > > It's a fairly simple component with a notable capability: support for file > storage on shared volumes such as NFS. We use this component to back > registered service files on NFS that are accessed from multiple nodes in > our CAS cluster. This allowed us to drop our database dependency entirely. > > If there is interest I'll file a Jira issue and formulate a pull request. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/**display/JSG/cas-dev<http://www.ja-sig.org/wiki/display/JSG/cas-dev> > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
