> The plugin cannot remain independent of the shell. The shell is the
> glue between 4D and the plugin.
I appreciate this, however, we've always been able to specify the names
far 4D method callbacks ('A4D Set Stream Callbacks').
I haven't used the A4D shells in their raw form for about 5 years and only
ever use them as a reference for how to call the plugin. This has never
been a problem since the plugin has (up till now) been independent of any
particular method naming in 4D. This makes it possible (for example) to
build real 4D components around the A4D plugin without conflicting with
any A4D library code.
It would be good if this level of independence could continue to be
supported (e.g. with a 'A4D_Set_httpBody_Callback' command).
Regards
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
