• Post Reply Bookmark Topic Watch Topic
  • New Topic

Ajax drawback ?

 
Marco Bertotti
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Moving an web based search application to ajax to improve user experience have some drawbacks.
Choosing from those what's the only one to consider ?

performance could require more hardware ? true ( due to the fact it will make more calls to the server) ?
accessibility could require more development ? true ( due to the fact i will make some browser buttons no more usable in the standar way) ?
security within the page ? false ( security in an issue when you communicato to the server due to all thing beeing passed not encripted but within the page should works just fine) ?
page navigability should be re-evaluated ? false ( due to just search no navigability is needed and and is 'absorbed' by the accessibility) ?
scalability requires redesigning the applications ? false ( it will require more hardware but not the redesign of the application) ?


What do you thing ? It seems 2 are almost 2 with the latter true ( accessibility could require more development ) beeing a major threat, isent it ?

Regards.
 
K. Tsang
Bartender
Posts: 3604
16
Firefox Browser Java Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
AJAX drawbacks hmm, given those answer choices, I will say:

Performance can be a drawback because network traffic increases hence server processing increases. However you need to know which performance is the question asking: client or server. If client then is it reasonable to increase hardware in the client computers? Unlikely.

Security actually is a drawback somewhat because users can disable javascript in their browsers making your page/app not functional. If talking about data within page, then it's considered safe. Yet during transmission data may not be encrypted.

Accessibility depends on browser setting for javascript I mentioned above in security. Getting the page to work properly (with or without AJAX) in multiple browsers is more functionality than accessibility.

Navigability is a pro because no page reload/submission/refresh hence improve user experience

Scalability has nothing to do with AJAX


So the answer to the question is security.
 
Marco Bertotti
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So i was totally wrong. I was thinking about Performance for the most.
 
Stephan van Hulst
Bartender
Posts: 6583
84
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
K. Tsang wrote:Performance can be a drawback because network traffic increases hence server processing increases.

Network traffic may actually decrease, because the client is able to perform calculations without having to reload the page. It depends on the application.

Security actually is a drawback somewhat because users can disable javascript in their browsers making your page/app not functional. If talking about data within page, then it's considered safe. Yet during transmission data may not be encrypted.

This should never affect security. AJAX has nothing to do with the underlying transport layer, or its security.

Scalability has nothing to do with AJAX

Actually a web application can become much more scalable using AJAX if heavy calculations would otherwise have to be made by the server.
 
Marco Bertotti
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Stephan van Hulst wrote:This should never affect security. AJAX has nothing to do with the underlying transport layer, or its security.

So it's related ONLY at the security within the page ?
 
Stephan van Hulst
Bartender
Posts: 6583
84
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't know what you mean by "security within the page".
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!