A 4th option would be to to autogenerate an (invisible) component and use it for handling the ajax requests.
I've no experience with your first suggestion and your 3rd doesn't convince me. I personally prefer using the 2nd (page variation) or the autogenerated component solution, depending on how the form is created and used, because: - passing the ajax-url to javascript via data attribute is easy and should probably be done anyway (instead of hard-coding a fixed url in javascript) - the scriptfile/modelClass, which handles the ajax-request, already has the (same) content Node/ContentMap, which may be needed, if a form is used on multiple locations with individual settings. Regards, Matthias -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=cf9da97a-a688-448b-8209-20f467979f04 ---------------------------------------------------------------- Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
