Hi Anthony, thanks for the feedback. So for the time being I will simply rely on FedOne posting the signer info. I was just about to implement an "Escrow store" which holds back submit requests until the certificate arrived. Would not make much sense right now.
I hope you did not change the entire federation protocol, because I just managed to get it up and running. Would be a pity to start all over again. But well, that's life when aiming at a moving target. Torben 2010/2/4 Anthony Baxter <[email protected]> > Nope. The post-signer request is for remotes to ask the hosting server > for signatures, not the other way round. FedOne _should_ be sending > the signer info first. We're making changes to the protocol soon so > that if a server needs a signature for a submit-request, it will reply > with a specific error code to the submit-request, saying "please > resend and include a signature". > We're most of the way through a major rewrite of the XMPP subsystem at > the moment, enabling much better handling of errors. Once I've ported > that to the fedone codebase, we can discuss the exact form that this > should take. > > Anthony > > On Thu, Feb 4, 2010 at 11:52, Torben Weis <[email protected]> wrote: > > Hi, > > I have a problem in my federation and can't figure out what is going > wrong. > > I used my C++ wave server (still has no name) to federate with a FedOne > > server. > > The wave in question is hosted on the C++ server. Delta-history etc. has > > already been exchanged successfully. > > Now FedOne submitted a delta (as you can see below). In response my C++ > > server has decoded > > the signed delta and extracted the signer-id. In the next step my server > is > > asking FedOne for > > the matching certificate by sending a signer-request. But FedOne does > never > > send a reply :-( > > I know that this signer-request is not necessary here because FedOne was > so > > kind to post it in advance. > > Nevertheless, this should work, or? > > Any suggestions what could have gone wrong? I am running out of ideas. > > > > INFO: sent XMPP packet: > > > > > > <iq type="set" id="5767-5" from="wave.wave2.vs.uni-due.de" > > to="wave.wave1.vs.uni-due.de"> > > > > <pubsub xmlns="http://jabber.org/protocol/pubsub";> > > > > > > <publish node="wavelet"> > > > > > > <item> > > > > > > <submit-request > > xmlns="http://waveprotocol.org/protocol/0.2/waveserver";> > > > > <delta > > wavelet-name="wave://wave1.vs.uni-due.de/w+1443540877/conv+root > "><![CDATA[CkwKGAgJEhRfhP62trKFvJ0d3cLzMOdYPvcmjhIXdHV4QHdhdmUyLnZzLnVuaS1kdWUuZGUaFxoVCgRiK2IxEg0KAigDCgMSAVgKAigGEqcBCoABiBrto+aa3AhZObPneAkNdSdQAPktNngVlSrQ2SbjxlQui9a4RwaV9gqx9697bphC85ZN1cH/ijOoGQQt0OfazG2c6wyvL2pZmTUfYrr0Qr5/h2ViAcXfph0thM5W8hrilxJkYvmZYx3+SLfqXcyxl/u7PTRVvIg3u/YwAR/nvZ0SIPe1gAqFD+Nk69ejajM1GzlN/+hJEd3OkIWWfQ7P8jLuGAE=]]></delta> > > > > > > </submit-request> > > > > > > </item> > > > > > > </publish> > > > > > > </pubsub> > > > > > > </iq> > > > > > > Feb 4, 2010 1:25:22 AM > > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > > processPacket > > > > INFO: received XMPP packet: > > > > > > <iq type="get" to="wave.wave2.vs.uni-due.de" from=" > wave.wave1.vs.uni-due.de" > > id="6191-3"> > > <pubsub xmlns="http://jabber.org/protocol/pubsub";> > > > > <items node="signer"> > > > > <signer-request > > xmlns="http://waveprotocol.org/protocol/0.2/waveserver"; > > signer-id="97WACoUP42Tr16NqMzUbOU3/6EkR3c6QhZZ9Ds/yMu4=" > > history-hash="X4T+trayhbydHd3C8zDnWD73Jo4=" version="9" > > wavelet-name="wave://wave1.vs.uni-due.de/w+1443540877/conv+root"/> > > > > > > </items> > > > > > > </pubsub> > > > > > > </iq> > > > > > > Feb 4, 2010 1:25:22 AM > > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > > processIqPacket > > > > INFO: key for this error is > > org.xmpp.packet.IQ:wave.wave1.vs.uni-due.de:6191-3 > > > > Feb 4, 2010 1:25:22 AM > > org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl > > getDeltaSignerInfo > > > > INFO: getDeltaSignerInfo for remote wavelet > > [WaveId:wave1.vs.uni-due.de!w+1443540877]/[WaveletId:wave1.vs.uni-due.de > !conv+root] > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Wave Protocol" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<wave-protocol%[email protected]> > . > > For more options, visit this group at > > http://groups.google.com/group/wave-protocol?hl=en. > > > > > > -- > Anthony Baxter, [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- --------------------------- Prof. Torben Weis Universitaet Duisburg-Essen [email protected] -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
