Home/ Questions/Q 747221
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T14:10:49+00:00

What are the things to consider and watch out for when designing a website

  • 0

What are the things to consider and watch out for when designing a website with AJAX? Must take care of conditions, say timeouts, error handling, for instance?

Best practices? What parameters to take care of while designing and coding?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There’s a few different views to consider:

    AJAXs Frameworks

    • There’s a few out there – I’m afraid I haven’t used many, but they’ll cover a lot of the plumbing for you, and handle X-Browser compatibility issues.
    • jQuery is a very commonly used one (so probably good for your CV).
    • ASP.NET AJAX if you’re on the MS platform.
    • Rolling you own can be instructive – but you’d only want to do it for the right reasons.

    Dependancies

    • Which browsers will be using the site and what do they support, all the old JavaScript X-Browser compatibility issues are applicable.
    • A good framework should help here.
    • Be careful how you manage dependancies between client-side code and server-side code; you want to ensure consistency as much as possible, and you want to avoid hard-coding stuff and baking in other garbage that will make maintenance and change hard over time.

    API / Interface Design

    Security

    • Publishing an AJAX API on the net has it’s own set of security gotcha’s, be wary of them.
    • Don’t trust user / system input, make sure you validate all calls being sent.
    • Don’t forget you can secure your API (or parts of it) in a secure part of the site. Uusers who have authenticated will also be authenticated to use any AJAX interfaces protected this way.

    Documentation

    • AJAX in itself doesn’t provide a way of describing itself (like Web Services can, via WSDL); I’v esometime had the server-side interace provide info on how it should be called if it’s not called correctly, or allow every interface to be called with a common parameter “Help” – when called it provides back all the information you’d need to know how to call it.
    • Your approach will vary depending on who can use/call the API: is it part of a web-app that will only work on the companies LAN, or is it puiblic/www facing?
    • 0