Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
8
Newest
 Teacher
Impact
~914 people reached

  • 0 posts edited
  • 0 helpful flags
  • 29 votes cast
Jun
3
revised Dictionary representation of an object
added 177 characters in body
Jun
3
comment Dictionary representation of an object
Most JS objects act as associative arrays or maps, but are typically not implemented as such, at least not in modern VMs.
Jun
3
awarded  Teacher
Jun
3
answered Dictionary representation of an object
Oct
1
comment Why were default and static methods added to interfaces in Java 8 when we already had abstract classes?
@Chris Multiple inheritance of state causes a bunch of problems, especially with memory allocation (the classic diamond problem)‌​. Multiple inheritance of behavior, however, only depends on the implementation meeting the contract already set by the interface (the interface can call other methods it declares and requires). A subtle, but very interesting, distinction.
Aug
12
comment Scheduling a few CPU-intensive tasks
@MartinSchröder Java EE. Delivering the data over REST for now (WebSockets later, likely). I'd be interested in making things fairly container-agnostic, so we can deploy to places like GAE and Azure.
Aug
12
comment Scheduling a few CPU-intensive tasks
@Snowman Took a look at it yesterday, and it looks like a fairly good solution. Need to test it and find a threading model that works well.
Aug
11
revised Scheduling a few CPU-intensive tasks
deleted 172 characters in body
Aug
11
comment Scheduling a few CPU-intensive tasks
@RobertHarvey It certainly is broad, hence being on programmers.se rather than SO. I was able to pare it down to two much more concrete points. Look better?
Aug
11
revised Scheduling a few CPU-intensive tasks
deleted 226 characters in body
Aug
11
awarded  Editor
Aug
11
revised Scheduling a few CPU-intensive tasks
deleted 17 characters in body
Aug
11
asked Scheduling a few CPU-intensive tasks
Jul
31
comment Client-side coding: How to prevent malicious use?
@Ajedi32 Clients are always inherently insecure, and if they probably aren't at the moment, you still have man-in-the-middle and all sorts of potential attacks, alternate clients, etc. You must never trust the client. If security matters on a particular operation, you do it on the server and deliver safe results to the client. What the client does after that is not necessarily your problem (if the client machine is compromised and logs traffic, you can't help that). You can still mitigate most data leaks by not sending the client anything it shouldn't have.
Jul
30
comment Client-side coding: How to prevent malicious use?
If I may elaborate on the first two sentences, the subtlety folks often miss is that point of client-side browser apps is to offload heavy lifting. Your server is still responsible for trusted operations, like sending emails or accessing the data. Having the client render a graph from that data, however, saves you CPU time (and money) without changing the security model.
Aug
22
accepted What other patterns can I use for this singleton?
Aug
22
awarded  Critic
Aug
22
awarded  Scholar
Aug
14
awarded  Autobiographer
Feb
16
awarded  Commentator