Lots of large institutions have keys that can open just one door or multiple doors, depending on how they're cut. Otherwise the guards would need to lug around a different key for each door.
esd
@esd
Best posts made by esd
Latest posts made by esd
-
RE: Douglas Havard hacks jail's network where he's an inmate
-
RE: Feeling a little Divvy
@Sir Twist said:
It is fine to use tables for tabular data. That's what they're for. They are bad and wrong for layout for accessibility reasons...
This is actually a myth. There is nothing in Section 508 that says you can't use tables for layout. And screen readers generally parse table-based layout just as well as a pure CSS layout.
-
RE: Mouse in the office
My old boss used to tell people that the very, very large cockroaches that scuttled around the basement (near the server racks) were crickets.
-
RE: Visual Studio wtf
@danio said:
Yes - also the accented I's (CD) on the same line are different to the ones on the line below, and the R next to the accented y is also quite strange.
I've never seen this before in the debugger. Wonder what caused it...
Windows tends to have trouble loading true type fonts when you're running low on virtual memory.
-
RE: The email address validation regexp
The problem in this case is that the RFC for email addresses is just quite a bit more complicated than most people realize.
I agree that following RFCs is good and I hate websites that reject perfectly valid addresses... but at some point you just have to say, "no, I will not allow comment fields in the middle of my email addresses." -
RE: Enterprise Webservice API (now with XML!)
I should also add that it doesn't escape any characters on the backend. So if any tags or even a "<" show up in the data, it makes life very tough on the parser.
Oh, and for any one-to-many relationships you either get: multiple identical columns or one column with all the data combined like "first item||second item||third item". As usual, it depends on the query. Pretty much every query is a special case. -
RE: Enterprise Webservice API (now with XML!)
I'd also like to add that, depending on the field, dates are stored in any of the following formats: "20060802", "2006-8-2", or, of course, UNIX Epoch.
-
RE: What's wrong with this site?
What a great idea! I'm trading in my CSS books for Photoshop.
-
Enterprise Webservice API (now with XML!)
I could write a whole book about the WTFs in software from this company. Actually, I should just post the manual. Here's one to start us off.
The API uses XML syntax over HTTP (or HTTPS) protocols, and any programming language that can make TCP/IP requests can be used to access the API. JAVA, PHP, ASP and many other languages include XML libraries that simplify the syntax of our API.
Hmm, that sound OK. Is REST? SOAP? Oh, I don't think so..
Using HTTP Post to the specified url with the following parameters: type=query and activity=query-data. URL encode the following payload:
<DATASET>
<SITE_ID>123</SITE_ID>
<MLID>345</MLID>
<DATA type="email">foo@bar.com</DATA>
</DATASET>the server responds with:
<DATASET><TYPE>success</TYPE>
<RECORD>
<DATA type="demographic" id="1">Foo</DATA>
<DATA type="demographic" id="2">Bar</DATA>
<DATA type="demographic" id="3">Baz</DATA>
<DATA type="extra" id="state">active</DATA>
<DATA type="extra" id="statedate">2006-01-01</DATA>
<DATA type="extra" id="uid">8474562938</DATA>
</RECORD>
</DATASET>Put every field from the query into a DATA tag--brillant! Then, take it a step farther and make it very difficult to figure out what the field name actually is (is it in "type" or "id"? Or is it one of the many special cases?). Awesome!
p.s. And if you make any mistakes in the query, it returns... nothing!