Re: [SignServer-develop] Questions

[Antoine L. <ant...@yo...>]

Hi Markus,

See my comments below.

Le 02/08/2012 19:34, Markus Kilås a écrit :
> On 2012-08-02 16:24, Antoine Louiset wrote:
>> Hi Markus,
>>
>> Thanks for your answer.
>>
>> I will of course share the dispatcher when I will develop it (scheduled
>> in october 2012).
> Great!
>
>> In fact, I do not realy understand what is a node...
> In this case I think a node means a server running SignServer. You could
> possibly have multiple servers/nodes behind a load balancer.
>
>> I will integrate in java the SignserverWS functionnalities. Do you
>> advice to use Client-SignServerWS or Client-SigningAndValidationAPI ?
> I would have used Client-SigningAndValidationAPI. That was what I used
> when I created SignServer-Client-CLI. For examples see for instance
> WebServicesDocumentSigner.java.
Very good, thanks.
>
>> The purpose of the process(String workerIdOrName, List<ProcessRequest>
>> requests, List <RequestContext> contexts) method is to set multiple
>> RequestMetadata from multiple contexts. Today, just one context is used
>> for all requests. I think it will be easy to implement in a
>> SignServer-Client project.
> Ok, but wouldn't you then want the first request to use the first
> requestContext and the next request the next one and so on? That would
> not be so easy to understand in the API, maybe then it would be better
> that the process method took only one list which contains pairs of
> ProcessRequest and RequestContext. Something like:
> ---
> List<ProcessResponse> process(String idOrName, List<RequestAndContext>);
>
> class RequestAndContext {
>     ProcessRequest processRequest;
>     ProcessContext context;
> }
> ---
>
> It would be simple to add a new method with something like that to the
> SignServer-Client-SigningAndValidationAPI project as it would only imply
> changes on the client sides and by keeping the old method it would be
> backward compatible as well.
Exactly ! I will certainly do like that. It's very easy to add methods 
in Client-SigningAndValidationAPI, a very good idea to develop this 
functionality.
>
> Best regards,
> Markus
>
>>
>> Good afternoon.
>>
>> Best regards,
>>
>> Le 02/08/2012 14:23, Markus Kilås a écrit :
>>> Hi Antoine,
>>>
>>> On 2012-08-02 08:31, Antoine Louiset wrote:
>>>> Hi Markus,
>>>>
>>>> I wonder if signserver could find the worker associated with the mime
>>>> type ? Could the dispatchers do this work ?
>>> There is no Dispatcher doing that currently but it is an excellent
>>> example of what a Dispatcher could be implemented to do. If you
>>> implement a new Dispatcher doing this we would be happy for the
>>> contribution.
>>>
>>>> How does the CallFirstNodeWithStatusOKWSClient work when the fastest
>>>> worker which respond does not correspond to the mime type of the
>>>> document to be signed ?
>>> I am not sure the CallFirstNodeWithStatusOKWSClient even consider that
>>> there might be multiple workers available on each node. I have never
>>> used it.
>>>
>>>> Is is scheduled to add a method process(String workerIdOrName,
>>>> List<ProcessRequest> requests, List <RequestContext> contexts) in the
>>>> SigningAndValidationAPI ?
>>> Is the purpose to be able to supply multiple documents to sign in the
>>> same request?
>>>
>>> There are no concrete plans for it at the moment but what you could do
>>> is to register an issue for a new feature and describe what the
>>> requirements are and how you suggest it could be implemented and we
>>> could keep it into consideration.
>>>
>>>> Could the default validator validate CMS signatures ?
>>> Not currently. There are only certificate validators and a document
>>> validator for XML signatures.
>>>
>>>
>>> Best regards,
>>> Markus
>>>
>>>> Thanks for your reply.
>>>>
>>>> Have a nice day !
>>>>
>>>> Best regards,
>>>>
>>>
>
>

-- 
Antoine Louiset                     Tél : +33 6 76 66 80 34
Responsable du projet Yousign       Mail : ant...@yo...