Hi Kris, I've already updated that gist with your comments.
Kris Borchers wrote:
> ## Open questions
> >
> > - Do we need a separate repository?
I would say no. This can just be part of aerogear-js repo.
+1 Makes sense to me
> > - Would the keys be automatically generated by default
during the
> > encryption process?
Not sure I follow you. Is this the same issue addressed above?
> > - What would be the best way to provide the keys for encryption?
Same question as above.
Duplicated questions, sorry. We already addressed that at
"API initial
definition"
> > - Will the AG JS crypto library be tied to AeroGear JS? For
example:
> > Users just looking for crypto, could make use of our work?
Yes I would tie it to AeroGear JS. If they only want crypto, it will be easy to use our
builder to only include the core and crypto bits.
Perfect!
I will move forward with that gist/code. Maybe we could start to file
Jiras on AGJS, to guarantee that I'm on the right track.
--
abstractj