[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dss-x] JMS transport binding
It sounds like there is some support for a standard profile, which is encouraging. I'll check what could be contributed from the customer project. Any other takers? Let's discuss after the holiday break. Pim -----Original Message----- From: stefan@drees.name [mailto:stefan@drees.name] Sent: 16 December 2008 07:57 To: kuehne@trustable.de; Pim van der Eijk Cc: 'dss-x' Subject: Re: [dss-x] JMS transport binding Hi Andreas, Hi Pim, kuehne@trustable.de schrieb: > Hi Pim, > > simple as expected. What to do next ? Start a profile or an > implementation ? an interesting question. Similar to the only post-version-1-added ebXML-DSS-Profile? >> The interface could be really simple, one in-queue for requests and >> one out-queue for responses. Four if separate queues are used for >> signing and verification. The DSS XML documents are transmitted as >> TextMessage payloads. >> For correlation the JMSMessageId and JMSCorrelationId should be set, >> based on the DSS RequestID. JMS has no payload container like MIME, >> so the document data should always be inline or use a file URI to >> point to some shared disk space. Wouldn't it be nice, to have another transport binding expl(or|ain)ed :?) Does this qualify as such ... I think so. What do you think? All the best, Stefan.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]