Would it be worth applying the patch anyway, with a note in the config that
this doesn't work with all clients (and is disabled by default)? That would
allow wider testing.
On 2012-01-29 23:01, Ali Lown wrote:
OpenSSL's s_client is also unable to connect when asked to use the TLS
cipher
I decided against a full palette as using it would make it difficult to get
the same colour selected twice, I kinda took all of GWaves HTML and CSS and
was going to use that as a basis for creating a new widget. Sounds like
there isn't much of a preference so I'll just plough on in then :)
On
Ok, good luck!
Let me know if you need any GWT help.
I think Id make it myself just from a composite of base widgets,
either as a disclosure panel with a vertical-panel containing a list
of colors, or as a gridpanel of some sort with little colored squares
to click on. But, again, no right way
All,
I have some free time to work on some patches. I am somewhat interested on
working on the server side of things, since I have done work on the client
before. I see a few issues with performance and also with persistence. Have
we captured the main issues that need to be addressed
Hi Michael,
I'd say start with persistence.
D
Il giorno 31/gen/2012 21:26, Michael MacFadden
michael.macfad...@gmail.com ha scritto:
All,
I have some free time to work on some patches. I am somewhat interested
on working on the server side of things, since I have done work on the
client
Maybe you can take a look at issue
https://issues.apache.org/jira/browse/WAVE-305
I made several attempts to fix it, but it's a bit elusive. It somehow
related to recent changes, as it didn't happen before with such frequency.
The problem is probably in the connection between client and server,
I hard disabled Websockets on my server looking into this issue, and
whilst it hasn't stopped it, it has certainly reduced its frequency.
- This fits in with the idea of it being related to a communications issue.
When it occurs though, the only solution is a server restart.
As for reproducing
You can reproduce it with the Selenium script. (You would need also this
plugin http://51elliot.blogspot.com/2008/02/selenium-ide-goto.html for
while loop)
Here are my findings regarding this problem:
The message No conversations is actually means that no conversational
wavelets were received
On 9 December 2011 00:09, Yuri Z vega...@gmail.com wrote:
I don't think that Linky should be implemented as robot/robot agent. I guess
you can just register
listener on update events and then insert the link annotation whenever text
in the edited blip looks like a URL.
I have now closed the
Any plans on moving to Java 1.7 support instead?
I just tested with openjdk-7-jdk-amd64 (on Debian), and found that the
ProtoBuf's failed to compile citing errors such as:
compile-proto:
[javac] Compiling 11 source files to /wave/build/proto
[javac]
Just a note: GWT doesn't support Java 7; but server-side code could use it
if needed.
Le 31 janv. 2012 22:57, Ali Lown a...@lown.me.uk a écrit :
Any plans on moving to Java 1.7 support instead?
I just tested with openjdk-7-jdk-amd64 (on Debian), and found that the
ProtoBuf's failed to compile
That would be a problem...
A quick google[1] suggests people were asking about it last July, but
that it was dependent on Eclipse's JDT having support (which it now
has), so it looks like it is just waiting for GWT.
Splitting the code between server + client has been needed for a
while, but I
I guess because robots then increase bandwidth(as the server needs to
send back the update befor you see it change). Probably would look
more laggy.
Id steer well clear of client side Regexs for something continuously
checked like this.
Why not just remember the last few letters typed? If its
Id steer well clear of client side Regexs for something continuously
checked like this.
I did precisely because I knew it would only end badly.
Why not just remember the last few letters typed?
If only that sort of information was available.
The API for this sort of thing is the
An idea to solve the speed problem:
There is no API for this currently, but it would be fairly straight
forward to listen to the operation stream coming out of the document, which
would give you precise, fine-grained knowledge of where changes are
occurring and what they are. The only issue here
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3709/#review4739
---
Can we break it into 3 patches and code reviews?
- Yuri
On
16 matches
Mail list logo
