kowsik

16 ms·

121.
by kowsik 16y ago
Dumping the JSON objects into CouchDB for static analysis should be a fun project.
122.
Don't use dumb packet-replay to test modern firewalls(labs.mudynamics.com)
2 points by kowsik 16y ago|0 comments
123.
Functional and Fuzz Testing Proxies and Load-Balancers(labs.mudynamics.com)
1 points by kowsik 16y ago|0 comments
124.
by kowsik 16y ago
Wow, reminds me of the pixel-a-dollar campaign to raise money for funding college. Can we see some source code please?
125.
CouchDB, DNS and Scaling on the Cloud(labs.mudynamics.com)
3 points by kowsik 16y ago|0 comments
126.
Introduction to Monads(defn.blip.tv)
3 points by kowsik 17y ago|0 comments
127.
Net Neutrality, GPL and Packets(labs.mudynamics.com)
1 points by kowsik 17y ago|0 comments
128.
Why NoSQL is bad for startups(labs.mudynamics.com)
9 points by kowsik 17y ago|1 comments
129.
Using Map/Reduce for Network Forensics and Troubleshooting(labs.mudynamics.com)
1 points by kowsik 17y ago|0 comments
130.
by kowsik 17y ago
Primary reason is, especially when used with something like CouchDB is absolutely no data transformation. What's in the DB is exactly what jQuery gets on the front end. See this: http://labs.mudynamics.com/2009/01/14/js3/
131.
Evolution of Testing(labs.mudynamics.com)
2 points by kowsik 17y ago|0 comments
132.
xtractr - Unleash the power of packets(labs.mudynamics.com)
1 points by kowsik 17y ago|0 comments
133.
Popcorn: Data Driven Testing using JSON(labs.mudynamics.com)
2 points by kowsik 17y ago|0 comments
134.
Multi dimensional data visualization(labs.mudynamics.com)
1 points by kowsik 17y ago|0 comments
135.
Collaborative Network Forensics(pcapr.net)
1 points by kowsik 17y ago|0 comments
136.
by kowsik 17y ago
Try "betty bought some butter it was bitter butter so she bought some better butter" ;-)
137.
Fun with Ruby case/when statements(labs.mudynamics.com)
2 points by kowsik 17y ago|0 comments
138.
Charlie and the Fuzzing Factory(labs.mudynamics.com)
1 points by kowsik 17y ago|0 comments
139.
by kowsik 17y ago
Couldn't resist thinking about this. Maybe it's just me and HTML forms. 1=1 will pwn you
140.
Large scale Ruby development with TDD(labs.mudynamics.com)
1 points by kowsik 17y ago|0 comments
141.
Fuzzing SCADA PLCs(labs.mudynamics.com)
2 points by kowsik 17y ago|0 comments
142.
IPv6 Fuzzing and Testing(labs.mudynamics.com)
1 points by kowsik 17y ago|0 comments
143.
Fuzzing in Javascript (using monadic functions)(labs.mudynamics.com)
1 points by kowsik 17y ago|0 comments
144.
by kowsik 17y ago
Hmm, then the timing is far too coincidental.
145.
by kowsik 17y ago
Ok, this is bizarre. Just submitted this link and it's by ontilt and not me... Why? Bug in HN?
146.
by kowsik 17y ago
C++ is so not perfect and is definitely not for large scale development. Read this: http://labs.mudynamics.com/2007/07/23/writing-c-within-ruby/
147.
by kowsik 17y ago
Also read this about native JSON: http://blog.mozilla.com/webdev/2009/02/12/native-json-in-fir... Which could make the speed comparable, but just on FF31
148.
by kowsik 17y ago
http://www.json.org/json2.js and here's the appropriate comment: // In the third stage we use the eval function to compile the text into a // JavaScript structure. The '{' operator is subject to a syntactic ambiguity // in JavaScr
149.
JSON, XML performance(labs.mudynamics.com)
15 points by kowsik 17y ago|7 comments
150.
by kowsik 17y ago
I can say only one thing: Switch to JSON. It's readable, you don't have to decide between attribute values and text and you get to save a (*)#$ of bytes. XML is so passe'.

More ›