What's the use of the C++ Server? I don't understand why I need it...
I'm using a "normal" wave server (XMPP with FedOne), which works quite
okay. But I can't search or add contacts with QWaveclient. When a wave
with another contact is opened, the contact is shown in the contact
list (tested with console client).
Will you just focus the development of QWaveclient on using the C++-
Server or will you work on the normal XMPP Server as well?
Hello,
I've got a few questions.
What's the use of the C++ Server? I don't understand why I need it...
I'm using a "normal" wave server (XMPP with FedOne), which works quite
okay. But I can't search or add contacts with QWaveclient. When a wave
with another contact is opened, the contact is shown in the contact
list (tested with console client).
Will you just focus the development of QWaveclient on using the C++-
Server or will you work on the normal XMPP Server as well?
> > I'm using a "normal" wave server (XMPP with FedOne), which works quite
> > okay. But I can't search or add contacts with QWaveclient. When a wave
>
> This is a limitation of the C/S protocol. We are waiting for google to
> specify a better one.
Okay, so searching isn't possible. But adding contacts should work, at
least it works when I'm using the console client.
Greetings.
Nothing happens, no errors or something. Adding images or gadgets
doesn't work neither. When I'm adding a gadget, it 's loading for a
short time, then it disappears. When I open the wave after that again,
it crashes. When I try to add images the insert button is disabled.
Contacts it's weird, what version of FedOne/ QWaveClient are you
using ?
Some gagdgets crash, but the Yes, No, Maybe gadget should work.
As for images there is a check that the address you give is indeed an
image, so if the url is incorrect, or no url the submit button is
disabled.
What is the url you give for the image ?
I've tried different versions, at the moment I'm using the newest
revisions of QWaveclient and FedOne.
> Some gagdgets crash, but the Yes, No, Maybe gadget should work.
> As for images there is a check that the address you give is indeed an
> image, so if the url is incorrect, or no url the submit button is
> disabled.
I've tried the Yes, No, Maybe gadget, it didn't work.
> What is the url you give for the image ?
I don't remember, I'll try it with another image.
I tried some other urls for adding images, but it never worked.
It seems FedOne wants <domain>!<id> as wave Ids to be opened but when
I tried opening <domain>!indexwave, FedOne does not complain but I
still don't receive anything in the client, so I really don't know
what is happening on their side.
As for the photos it doesn't work on current version of FedOne but it
does work on version 137. I guess they changed handling of
annotations.
Cheers,
Nicolas Patry
On Mar 4, 11:45 pm, Torben Weis <torben.w...@gmail.com> wrote:
> Which revision are you using now?
>
> Greetings
> Torben
>
> 2010/3/4 Rebekka H. <rebekka.heckf...@web.de>
>
> > After re-compiling the newest version of QWaveclient, nothing was
> > working with the newest version of FedOne. So I tried an older version
> > and now it works again, adding contacts works, too.
>
> > I tried some other urls for adding images, but it never worked.
>
> --
> ---------------------------
> Prof. Torben Weis
> Universitaet Duisburg-Essen
Here is the output I got from the FedOne server as soon as I inserted
the image.
24-Mar-2010 11:01:06
org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl
isLocalWavelet
INFO: ### WS is local? [WaveId:wavybox.co.uk!w+433745266]/
[WaveletId:wavybox.co.uk!conv+root] = true
java.lang.IllegalStateException: Attempt to build ill-formed operation
(ViolationCollector[2: ill-formed: characters is empty at original
document position 3 / resulting document position 5]): __3; << image
{ attachment="a+9559970" }; << caption {}; ++""; >>; >>; __1;
at
org.waveprotocol.wave.model.document.operation.impl.BufferedDocOpImpl.checkWellformedness(BufferedDocOpImpl.java:
84)
at
org.waveprotocol.wave.model.document.operation.impl.BufferedDocOpImpl.create(BufferedDocOpImpl.java:
59)
at
org.waveprotocol.wave.model.document.operation.impl.DocOpBuilder.build(DocOpBuilder.java:
54)
at
org.waveprotocol.wave.examples.fedone.common.WaveletOperationSerializer.deserialize(WaveletOperationSerializer.java:
391)
at
org.waveprotocol.wave.examples.fedone.common.WaveletOperationSerializer.deserialize(WaveletOperationSerializer.java:
291)
at
org.waveprotocol.wave.examples.fedone.common.WaveletOperationSerializer.deserialize(WaveletOperationSerializer.java:
258)
at
org.waveprotocol.wave.examples.fedone.waveserver.LocalWaveletContainerImpl.transformAndApplyLocalDelta(LocalWaveletContainerImpl.java:
94)
at
org.waveprotocol.wave.examples.fedone.waveserver.LocalWaveletContainerImpl.submitRequest(LocalWaveletContainerImpl.java:
68)
at
org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl.submitDelta(WaveServerImpl.java:
572)
at
org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl.submitRequest(WaveServerImpl.java:
396)
at
org.waveprotocol.wave.examples.fedone.waveserver.ClientFrontendImpl.submitRequest(ClientFrontendImpl.java:
239)
at
org.waveprotocol.wave.examples.fedone.waveserver.WaveClientRpcImpl.submit(WaveClientRpcImpl.java:
132)
at org.waveprotocol.wave.examples.fedone.waveserver.WaveClientRpc
$ProtocolWaveClientRpc$1.submit(WaveClientRpc.java:1682)
at org.waveprotocol.wave.examples.fedone.waveserver.WaveClientRpc
$ProtocolWaveClientRpc.callMethod(WaveClientRpc.java:1793)
at
org.waveprotocol.wave.examples.fedone.rpc.ServerRpcController.run(ServerRpcController.java:
199)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
24-Mar-2010 11:01:07
org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider$Connection
$1 run
INFO: error = java.lang.IllegalStateException: Attempt to build ill-
formed operation (ViolationCollector[2: ill-formed: characters is
empty at original document position 3 / resulting document position
5]): __3; << image { attachment="a+9559970" }; << caption {}; ++"";
>>; >>; __1;
I'm using qwaveclient rev299.
Do you have problem displaying the image on the receiving client?
cheers,
Chiang
To unsubscribe from this group, send email to qwaveclient+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
You are correct, in order to connect QWaveClient to FedOne, you have
to pass indexwave!indexwave. I just built QWaveClient on windows (not
for the faint of heart) because the version on the site didn't have
this update and I wanted to continue to run QWave against FedOne.
Once I made that change in networkadapter.cpp I was able to federate
with wavesandbox. I ran two local instances with QWave and one remote
on wavesandbox. It was an overall success, but I did run into a
couple of issues:
- Replies between wavelets did not display on the sandbox. If I
continued in a new thread or updated an existing wavelet, I could see
the change. When I refreshed wavesandbox, the changes did appear
(could be a sandbox issue). QWave client's did not have a problem.
- The image did not display to the sandbox client. And once I added
the image, I could no longer see any updates on the sandbox (I could
see the image and updates on my other local QWave client).
I also ran into a couple of other issues in general:
- I could not get a gadget to show (specifically the yes/no/maybe). I
would see a notice saying the gadget was loading, it reserved the
space, but the gadget never appeared.
- When I type in the search box denoted by "in:inbox" and press enter,
nothing happens.
Are these issues seen in any other platform? Is it based on me
running against FedOne? It could also be a result of my build.
Everything else seems to be working great. Thanks a lot for your work
in this area.
R,
Anthony
On Mar 4, 11:26 am, Torben Weis <torben.w...@gmail.com> wrote:
> Hi,
>
> I saw a patch in FedOne telling that the indexwave got a fake domain. When
> sending the ProtocolOpenRequest we should try asking for
> "indexwave!indexwave" instead of "!indexwave". And most likely QWaveClient
> does not recognize the indexwave because it has this fake domain.
>
> In case of a doubt, running wireshark on the FedOne console client will show
> what they are doing now.
>
> Greetings
> Torben
>
> 2010/3/4 Nicolas <patry.nico...@gmail.com>