[Neuclear-develop] Tasks Ahead

[Pelle B. <pe...@ne...>]

Hey Deneb,
> Can i work on the distribution controller in the
> payment module ?
Please go ahead with the DistributionController. We need to first work out 
some of the requirements for it. I havent 100% got it squared away in my mind 
yet. I'll start a thread on the mailing list where we can work out what it 
needs to do. I think if you worked on the PortfolioManager first it would 
give you a good insight into how everything works. It should only take a 
couple of days.

> also reagrding the servlet signer .. is there a
> servlet made already or should i make a new one ..
>
There already is a SigningServlet in org.neuclear.id.signers.SigningServlet, 
which uses a regular agent such as the SwingAgent. This is what is used in 
the Personal Signer. However for regular use on a public web server there is 
a subclassed version called DemoSigningServlet which handles the signing in 
two phases:
- Phase 1 Present data to be signed and passphrase box
- Phase 2 Accept Passphrase and Sign

So I would recommend that we use that one as starting point if you want to try 
it out. Obviously we want to add more to this than just a passphrase. For 
security reasons. But in the next rev.

> in the sitre.. i think u have used the jce signer ..
> would it be recommended to use the sql signer ?
It would really depend on how many assets you would be managing on your 
server. In an environment where you need to manage large amounts of keys, the 
SQL Signer would be the recommended. If you only have one asset and therefore 
one key on your server a JCE would be easier to maintain.

-P
-- 
http://talk.org      + Live and direct from Panama
http://neuclear.org  + The World Wide Web of Assets