121–126 of 126 posts
Earlier quoted context omitted.
I’m no security expert. How is “exposing the hash seed” a problem for the vast majority of applications? What timing information would be leaked and why would that be problem? On the other hand, accepting unsorted maps seems like it could introduce covert channels?
https://bugzilla.redhat.com/show_bug.cgi?id=750555 This led to hash randomization on by default since Python 3.3.
(I've used both DataPower and COBOL - I've got a healthy respect for robust, long-lived legacy systems). I must admit I was scratching my head on this. The JSON spec might not specify order, but the serialized JSON is ordered by nature. JWT needs it for example (and I'd assume many signature models). Or you might have a caching layer that needs it. Maybe unchecking this causes the legacy backend to get hammered? Ther…
Justgoogled DataPower, out of curiosity, and I found XML Accelerator XA35. I did not know there is HARDWARE for XML PROCESSING! Blows my mind.
Earlier quoted context omitted.
Granted, it came from there, but that was back in the days of map=eval(json) and they're gone. There is nothing in json the format (as opposed to json the language construct) to impose the unordered behavior.(Or, for that matters, the 'no comments' bit).
> There is nothing in json the format [..] to impose the unordered behavior That's not true. The spec at http://www.json.org/ says "An object is an unordered set of name/value pairs".
The backend polled an API that served XML updates on game scores etc. Note that I didn't previously know anything about baseball (and I still don't, not really).
So let's say that a baseball team scores a Double. We'd see some XML like .
Now, suppose a team scores a tripple... You know that there's a entity. What would you expect to see inside the node?
If you're me, you'd expect to parse .
I got the call during dinner. There was an important game happening, and the app suddenly broke. People were uptight. They loved our app and they were complaining.
In the end, it turns out that we would need to process . Why? "Oh, it's always been that way." (Says the brusque developer at the service charging $50k/month for access to this feed.)
Earlier quoted context omitted.
In other words: why GUI configuration systems should allow comments, just like text config files do.
Underrated idea. Never seen this, but I would kill for the ability to add comments to configuration settings or even log changes with commit messages.
Earlier quoted context omitted.
Justgoogled DataPower, out of curiosity, and I found XML Accelerator XA35. I did not know there is HARDWARE for XML PROCESSING! Blows my mind.
Yep, back in the SOAP days we used to have a lot of XML flying around that would need to be converted into one format or another via XSLT. You can certainly run XSLT on a piece of XML in your own code, but having a dedicated piece of hardware do it for you with a slick GUI was always an easy sell for IBM to management.
Was it a HTML Gui with file upload and everything? Or just some server, port and proprietary protocol?
Maybe these things are on Ebay for cheap. Oh, that looks like fun.