G'day:
Bloody hell: fifth one today. And I've got a sixth one to come (another bloody stupid ColdFusion bug... stay tuned...).
My previous article described the mooted solution to our serialisation challenge, but it did not have an end-to-end code example.
Tuesday, 2 July 2013
There's always another bug...
G'day:
Whilst playing with
This is just a bug (NB: in ColdFusion 9.0.1+. But not Railo).
Whilst playing with
objectSave() and objectLoad() yesterday, I came across yet another bug in ColdFusion. It really does seem sometimes that if one attempts to do anything other than the "obvious" in CF, there are bugs. Or illogical quirks. Or omissions in the implementation.This is just a bug (NB: in ColdFusion 9.0.1+. But not Railo).
Serialisation woes resolved: "screw JSON"
G'day:
(third one today... the other two were only wee ones, so hardly count).
Right, so you might've read me wittering on about "ColdFusion vs JSON. How to make a developer cry". I needed to serialise some data to put it in a cache, and ColdFusion 9's JSON-handling is not up to the job.
What were were trying to do is to reliably serialise a query, and have ColdFusion not mess up either the null values, nor the dates (actually the latter is a side-effect of the JSON processing, and more an issue with query of query).
I was trying to use JSON because it was faster and lighter than WDDX, and it's kinda become the de facto way of doing quick serialisation, I think.
Yesterday I was forced to write this email to my superiors:
(third one today... the other two were only wee ones, so hardly count).
Right, so you might've read me wittering on about "ColdFusion vs JSON. How to make a developer cry". I needed to serialise some data to put it in a cache, and ColdFusion 9's JSON-handling is not up to the job.
What were were trying to do is to reliably serialise a query, and have ColdFusion not mess up either the null values, nor the dates (actually the latter is a side-effect of the JSON processing, and more an issue with query of query).
I was trying to use JSON because it was faster and lighter than WDDX, and it's kinda become the de facto way of doing quick serialisation, I think.
Yesterday I was forced to write this email to my superiors:
Adobe ColdFusion bug tracker: sigh
G'day:
(Warning: this is just a frustrated grumble, and has little merit beyond allowing me to stomp my foot like a petulant school child).
As mentioned in my previous article, "I've raised four bugs, but unfortunately I cannot share the details with you because I raised them as "security issue", so I don't get given the bug number."... all I get is a note "Thank you for submitting a bug. Due to security concerns, this bug will not be externally viewable."
This plumbs new depths of "Adobe really just don't think shit through".
(Warning: this is just a frustrated grumble, and has little merit beyond allowing me to stomp my foot like a petulant school child).
As mentioned in my previous article, "I've raised four bugs, but unfortunately I cannot share the details with you because I raised them as "security issue", so I don't get given the bug number."... all I get is a note "Thank you for submitting a bug. Due to security concerns, this bug will not be externally viewable."
This plumbs new depths of "Adobe really just don't think shit through".
ColdFusion: WebSocket security issue: status update
G'day:
Just a quick one. There's been some feedback from Adobe regarding this web sockets security issue. As a comment against that article, Awdhesh says:
Just a quick one. There's been some feedback from Adobe regarding this web sockets security issue. As a comment against that article, Awdhesh says:
We are working on it and the fix will be available in next updater for CF10.
Monday, 1 July 2013
Subscribe to:
Posts (Atom)