client-side

问题 I've looked at Google Translate but from what I can tell it only offers a client-side JavaScript API for freely translating text between languages. What I need to do is translate text on the server side in Java. Is there a library that makes it possible to do this for free with Google Translate? 回答1: Here is a Java API... http://code.google.com/p/google-api-translate-java/ and just for reference, a PHP implementation - http://code.google.com/p/gtranslate-api-php/ 回答2: There is nothing

问题 In this stackoverflow post i read about filtering backbone collections and using subsets. One answer (by sled) recommends using backbone.subset.js (usage example). I could not find any further resources on backbone.subset.js and I failed implementing it into my project. It seems like backbone.subset.js is the perfect solution for what i'm trying to achieve. (Having one "parent" collection that holds all models at all times, and depending on user input filtering the relevant models from the

问题 I need to delete clientside cookies with the same name but with different paths. What is the best way to do this in javascript. 回答1: Just specify the same path of the cookie you want to remove, giving it a past expiration. document.cookie = 'name=value1; path=/'; document.cookie = 'name=value2; path=/path/'; alert(document.cookie); // name=value1; name=value2 document.cookie = 'name=; path=/path/; expires=' + new Date(0).toUTCString(); alert(document.cookie); // name=value1 Changing it to

问题 I need to delete clientside cookies with the same name but with different paths. What is the best way to do this in javascript. 回答1: Just specify the same path of the cookie you want to remove, giving it a past expiration. document.cookie = 'name=value1; path=/'; document.cookie = 'name=value2; path=/path/'; alert(document.cookie); // name=value1; name=value2 document.cookie = 'name=; path=/path/; expires=' + new Date(0).toUTCString(); alert(document.cookie); // name=value1 Changing it to

问题 If you were to hash a user's password prior to sending it across the line and leaving it in plain-text in memory, would this improve the security of the application? I would assume this mitigates a small fraction of vulnerabilities by protecting the data stored in the clients memory. But really if we're worried about someone reading the client's memory there are probably bigger problems that we can't address. There's something that doesn't feel right about hashing on the client's end. Is

问题 If you were to hash a user's password prior to sending it across the line and leaving it in plain-text in memory, would this improve the security of the application? I would assume this mitigates a small fraction of vulnerabilities by protecting the data stored in the clients memory. But really if we're worried about someone reading the client's memory there are probably bigger problems that we can't address. There's something that doesn't feel right about hashing on the client's end. Is

问题 I've written the following small piece of javascript (Based on the excellent parseURI function) to identify where the user originated from. I am new to Javascript, and although the code below works, was wondering if there is a more efficient method of achieving this same result? try { var path = parseUri(window.location).path; var host = parseUri(document.referrer).host; if (host == '') { alert('no referrer'); } else if (host.search(/google/) != -1 || host.search(/bing/) != -1 || host.search(

问题 I've written the following small piece of javascript (Based on the excellent parseURI function) to identify where the user originated from. I am new to Javascript, and although the code below works, was wondering if there is a more efficient method of achieving this same result? try { var path = parseUri(window.location).path; var host = parseUri(document.referrer).host; if (host == '') { alert('no referrer'); } else if (host.search(/google/) != -1 || host.search(/bing/) != -1 || host.search(

问题 This is a follow-up to, or rather replacement for, this question: MVC/ASP.NET: Client side validation not working The issue was, and is, that my ASP.NET/MVC client-side validation isn't being performed, even though it should. Now that I've done more testing, it seems I have identified the core of the problem, so here goes. I have a ViewModel as follows: public class RegisterViewModel { [Required] [EmailAddress] [Display(Name = "Email")] public string Email { get; set; } // some other

问题 Some days ago, I asked a question , that was: How could anyone return the default value to a predefined JavaScript object or function (like the object window.console, or the object-function document.getElementById) once it has been changed? Posted here: Return the default value to a predefined javascript object The solution wasn't enough, because the possibility to return the default value was based on creating an iframe object and insert it to the current DOM. But, we also have the