Wedge

I suspect it isn't, actually. Take Nao, for example... before he worked with Aeva and SMF, he worked on Kyodai Mahjongg which IIRC was written in Delphi - which is just another iteration of Pascal.

I think, though, if you look you'll find a lot of similar concepts in PHP, it's derived from C and a *lot* of languages have similarities.

It's not obvious, no.

What happens is that the Tapatalk code is adjoined to the forum and the app specifically contacts the extra code, rather than contacting the normal main forum code. It's a bit more complicated than that, but that's the nuts and bolts of it.

The fact that you can only find a forum through their site is mostly to get round a rule in one of the app stores' rules (probably Apple's)

Yes, remove DB caching and if any caching is going to occur, do it via cache_put_data if (isset($settings['cache_level']) && $settings['cache_level'] >= 2)

That would imply then that you want to extend the TTL on caching so that you do fewer writes.

You could leave the caching subsystem in, but only cache things if it's level 2 or higher (so that you actually have to have a proper memory cache in order to use it)

Implementing it without requiring a reload is something I meant to do just didn't get time to write the JS for it.

Note that all suggestions of 'silent like' are completely different to what you're suggesting.

The fact it's the webserver, really. Installing Apache is piss-easy, building anything even modestly complex in Node.js tends to invoke lots of things on top. For example, I'm using Express to handle routing and certain types of errors, but even that requires some work to do anything intricate that isn't 'out of the box'.

The other thing is that you have to be careful about how you do things. Node itself is a single thread, and the idea is that for any I/O operations you're supposed to branch off, letting a subprocess perform the I/O (which includes DB queries for example) and handle the result as a callback; the idea is that instead of having to wait around for queries to complete, you don't block the process from working and allow the main process to process other requests.

It's an interesting process if you're not used to writing in that manner, because while it is much like the JS you'd write in the client of 'kicking something off and getting a callback when it's done', you really have to do that a lot more and as you can imagine anything with any complexity is going to require multiple nested callbacks, even with some of the abstracted stuff going on to make it simpler.

The one thing I'd note is that most folks using Node aren't using conventional DBs either, but using things like CouchDB and MongoDB (Mongo is more what I'm looking for, and there is a lot of advantage to having JSON for adding objects and nesting objects inside them)

Also imagine that you have to do a lot more of the session handling sorts of things yourself (though Express does some of that for you)

Node.js is a tool for specific caseloads, rather than a general deployment.

I think this is a fairly unlikely situation to actually want in the core, personally. I could see it being a plugin though.It would have to be a change to the query/processing to hide it from others that aren't you, whilst including you in it but the schema change is simply the extra column.

I'm not sure, there is such a thing as having too much stuff.Try it :)I uploaded it, saw it was corrupt, removed it, reuploaded it and still corrupt (the same way). Very weird. But I didn't find any of the normal PNG block indicators, I couldn't find the IHDR sector end when downloading the file again...