From: Marc Groot Koerkamp <marc@sq...> - 2006-10-17 19:38:54
Hehe, time to reply.
On Mon, October 16, 2006 2:58 am, Paul Lesniewski wrote:
> On 10/15/06, Steve Brown <sbrown25@...> wrote:
>>> I just talked a bit with Iavor on #squirrelmail after I got the
>>> message below. Iavor offered a few years back also his help on
>>> templating squirrelmail but at that time we were not ready for it.
>>> He is aware of current roadmap of squirrelmail and he thinks that at
>>> this moment it's a good time to do a parallel design of an ajax
>>> templates. I think he is right because the sm-core need to accomodate
>>> ajax and while we are in the middle of rewriting a lot for our
>>> templates it's probably also a good time to think about ajax.
>>> Iavor will start a wiki page with
>>> a) possible items to be AJAXed b) review of the AJAX technologie c) List
>>> of possible AJAX-to-server request.
>>> Aspect c hooks into sm-core so that part is important because it
>>> probably could lead to api changes or a middle layer to handle the
>>> ajax requests.
>> Heh, Paul and I have actually been discussing this off list for the
>> last few days. We threw around a few ideas: API to do it, plugin to do
>> it, etc. Most of the stuff that has been discussed here. We didn't
>> really decide anything, just threw some ideas around.
>> My thoughts were tending towards having a defined set of functionality
>> that can be AJAXed then having all of those functions be accessed
>> through, e.g. src/ajax.php, Format of the request can tak e a variety
> Not "ajax". Should be more generic. Also, I think the API has the
> potential to outgrow a single file and is better placed in its own
> directory (or again, a plugin).
>> of forms, but probably the easiest would be through GET vars. For
> I don't think that kind of restriction is either necessary or
> relevant... POST can work just as well and can be supported entirely
> dependent on the type of request. The more interesting conversation is if
> we could or would want to support a request that comes wrapped in XML!!
> Hmmm.... Not sure it's necessary in the end, but...
>> example: src/ajax.php?action=delete_message&message_id=10. Some of
>> the functions I could see being AJAXed:
>> delete mesage send message folder message counts move/copy message message
> We could instead migrate the ENTIRE SquirrelMail page request system
> at the same time, so that both "normal" HTML page requests AND these more
> low-level granular requests go through a *single* access point, which
> dispatches requests as either a normal page request (at least for now
> include the normal src file and exit) or as an "API" request....
> Not sure if that's desirable (but maybe it could be helpful for
> security concerns too?), but just thinking out loud.
Yes that's desirable. One single access point and at the same time get rid
Marc Groot Koerkamp