-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add gwan to bigtable benchmark #37
Comments
Hi redaready, thank you very much for that code. I assume that it will give us a great performance baseline. However, from what I understand of your code you are neither using UTF-8 encoding nor are you HTML escaping the dynamically generated table content. I understand that for the numbers in the bigtable benchmark escaping is unnecessary. However we do the escaping, as the benchmark should reflect the performance in real use cases as good as possible. For many real use cases, its very hard and error prone to get rid of escaping dynamically generated content. best regards and thanks again, |
I totally agree with you about escaping the content and just updated the code for g-wan 2.0+. I think the string of gwan has the same encoding as the source file.....i am waiting for the more-than-expected release of gwan to test the changes of api and performance. |
Thanks for updating the code. I had a quick glance at it and I'm surprised that there's no way to do a |
hi, did you add g-wan to your benchmarks? |
No we did not do that yet due to a lack of development ressources. We'd however happily accept patches..as usual :-) |
Sure thing, I was just curious because the patch above looked good to me.
to printf into the console you can simply These are other "html_escaping functions" available in G-WAN:
|
Pierre,the creator of gwan, has written a better version cf:https://gist.github.com/2001619 |
Thank's I'll look into that. |
https://gist.github.com/878224
feel free to add it in your benchmark.
gwan:http://www.trustleap.com/
The text was updated successfully, but these errors were encountered: