Tag Info

Hot answers tagged

11

Since you are using this information for billing purposes, I do not see why you would not want it in the database where it can be easily queried, aggregated, reported on, and joined to other data. I also think it's much easier to maintain a single database table containing the log information than a bunch of separate log files. Same with your concern ...


9

I agree with the comments that he was likely looking for HTML5 local storage, and may have expected you to have experience with it. Frankly, unless it was an integral requirement of the job and you stated you had experience with it, his expectation and reaction were unreasonable, in my opinion, for anyone with any amount of experience. Why? Because, three ...


6

The 'correct' answer - at least, the one they were looking for - was indeed HTML5 LocalStorage (an excellent link by Steven Burnap). And the interviewer was probably being...well, I believe the technical phrase is "a bit of a knob". This is basically arrived at by process of elimination, in that a cookie cannot be anywhere near big enough, sessions are ...


2

I think this varies from project to project. Generally the advise by Bart is a valid one. If these assets are directly connected to the source-code and managed by the developer (best example are images statically linked/embedded in a template) it's a good practice to have them inside the repo. If this isn't the case, we have to ask some other questions. ...


1

I would recommend separate databases for the applications and one database for the user accounts. I would put any fine-grained access control within the individual applications. I would also look to make the one 'user database for the user accounts' be accessed via an authentication service using industry standard protocols such as LDAP.


1

There are a couple of ways to approach this, depending on your requirements and scale. First of all though, I don't believe a CDN is appropriate in this case. A CDN is used for caching of static documents to provide faster delivery of those assets to end users. It's not relevant for centralised storage or management of files. At the larger end of solutions ...


1

Even though this could work, this might be a little overkill. Will issues in scalability still arise in modern Prolog implementations? Beware of strings. In some implementations, the generated code for querying in_group/2 will result in a lot of branching, as in if "Alice" then ... else if "Bob" .... Replace double-quotes with single-quotes, ...


1

You could use NodeJS and the node package module Socket.io for this. Separating the tasks of client connections and creating/returning dynamic web pages into node modules could work the way you described. Node describes their modules in their API docs. The book NodeJS in Action has some projects that perform similar functionality (even the basic ChatApp in ...



Only top voted, non community-wiki answers of a minimum length are eligible