As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I was preparing for the interview and I stumble across this question.
Can anyone explain me what are the Benefits of Ajax Calls,
why do we need Ajax Calls and what can be the disadvantages of Ajax.
Any suggestions will be appreciated.
Most importantly, do you understand what AJAX is? If not, I would start by reading through http://en.wikipedia.org/wiki/Ajax_%28programming%29 .
One large benefit is that it allows for partial updates to pages, without requiring a reload of the current page or a load of a whole new page with each action or input, as was typical in years past.
One disadvantage may be some additional complexities, development time, and troubleshooting. (The above Wikipedia link actually contains a list of 10 drawbacks for "disadvantages".)
Ajax calls can help you decrease website load. for example if you want to load a customers table from database ajax can load it in without refreshing your css and images etc... so you can save memory by using ajax.
disadvantage of ajax is ... it's taking too much time in development and little bit hard for basic users
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Ours is a java web application on struts2 framework. Currently for contact us form and download reports form we are using Recaptcha. We have to refresh the captcha at least 4-5 times to get the readable words. We are looking for some simple alternative to Recaptcha which prevents getting Spam requests.
Guys can you suggest me a replacement for Recaptcha.
Yes, another example of an alternate captcha is this: you can make a slide of images, and place one behind the slider. Then, let the human chose from the slider which image is behind the slider.
(I have seen it in a forum, but I don't remember the name of website where I have seen this type of captcha)
You can also make your forum like no one can copy paste anything there, means pasting is restricted there.
I found this! http://areyouahuman.com/
Just discovered it. Plan to use on my next project.
Images are far more easy to identify compared to garbled text. They are more difficult to break too. You could use image-identification CAPTCHAs such as these.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Each time, when we type the key-words in Google, how does Google give us its answers?
I want to know the process of how Google process our requests.
Personally, I assume that:
1.there are a huge amount of queries sent to Google, in order to respond ASAP, Google gotta have some kinda distributed system, right?
2.also, I think there are some kind of cache systems to speed up Google's response speed, right?
3.If cache indeed exists, what is stored in that cache? Could it be some kind of <key, value> pair? Cuz I guess that, it's <key-words, url>. But would be it be too expensive to cache url directly, because each url will probably take up many memory, right?
UPDATE:
After skimming the keynote suggested by #Gregory Pakosz, I wondering what the Cache Server is responsible for and what the Cache Server caches?
Jeff Dean's 2009 keynote: Challenges in Building Large-Scale Information Retrieval Systems gives a pretty nice overview of how Google works.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am trying to develop a web based document browsing system, that could look possibly something like : http://www.cell.com/trends/biochemical-sciences (then click on "Protein kinases: evolution of dynamic regulatory proteins").
What web technologies should I look at using? AJAX?
Thanks in advance.
Andy
AJAX could do the trick, but you'll need more than that.
Getting document sections and pictures with AJAX is half (maybe less than half) the job, as you'll need all the backend code to upload documents, maybe extract document sections from PDF, store documents hierarchically, retrieve the document hierarchy and pictures, and so on.
Moreover, you don't even told us what server-side technology you are going to use... Java, PHP, DotNet... and the database... PostgreSQL, MySQL, SQL Server, Oracle, end the list goes on.
About the AJAX side and web UI, I suggest you take a look at jQuery and jQuery UI.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
I know that there are lots to read on the net about AJAX , but if U want to explained it for a non-web-technical person what would you say ?
"A style of web page where you can edit stuff without having to wait for the whole page to reload all the time"
It's a mechanism to communicate with webserver (backend) without refreshing the whole page. :)
But I believe this site is not a good place to ask these kind of questions.
"A way of updating a web page in sections, instead of all at once."
It's a technology that allows you to download only select portions of the web page, providing a faster and less disruptive page update.
Prior to AJAX, if you need PEN, you must have to buy PAPER and other things which you already have.
In AJAX, you get what you need.
A technique which escape your server from extra burden and fasten your responses
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
If I built a page that consisted of IFrames on the order of hundreds, would this be incredibly slow, or would it behave similar to having a hundred divs?
The reason I ask is I'm looking for a nice recursive way to build a web page, where I can load sub-elements of a page as if they were complete pages of their own, with their own urls.
Thoughts? Opinions? Am I totally crazy to even be thinking it?
Edit: I just realized this would probably absolutely shred the network connection because it would have to make separate requests for each embedded frame, wouldn't it? And everything I've learned on making web pages more efficient to load is to reduce the number of http requests it needs to make.
yes, indeed-- browser must make separate requests for each embedded iframe.
This isn't purely related to efficiency, but there are also various gotchas like the Body OnLoad not firing until every single IFrame in the page hierarchy has fully loaded first.
If you need things inside the IFrame javascript to be able to "call out" to another IFrame or the main page this can also cause maintainability and readability problems.
It will be slightly more efficient than opening hundreds of web browsers, and only slightly. You will still be rendering the pages you load in the iframes and this takes memory.
I find difficult to communicate between iframes (in javascript for instance).
I prefer divs instead and you can use a server cache where you need it.
Maybe a solution which uses partial rendering with Ajax can be more elegant.