23 Aug 2009 2:58 PM #1
On Friday I built my first two Server Stack backends for Ext.Direct in Perl.
The first implementation (called simple) is there as a reference implementation. It is a useful source to help get you started porting Ext.Direct functionality to your own framework.
The second implementation (called modperl) is a more complete and functional implementation, and because all classes are loaded at Apache start time, it is quite fast.
I have not completed all functionality (e.g. file uploads).
- http://scott.dd.com.au/wiki/Ext.Direct - to see a description
- http://github.com/scottp/extjs-direct-perl/tree/master - for GitHub source
- http://github.com/scottp/extjs-direc...zipball/master - for a Zip version
- http://scott.dd.com.au/demo/extjs-di...st/simple.html - Live demo (including field validation)
- http://github.com/scottp/extjs-direc...er/README.TODO - TODO list
- 27/August/2009 - support for before/after hooks & form post data
24 Aug 2009 12:17 AM #2
Cool. How about to CPAN it?
24 Aug 2009 2:34 AM #3
CPAN is the plan... I like to put it up only once it is working though, so give me a day or two :-)
24 Aug 2009 2:38 AM #4
Sounds good, will be glad to help if needed.
24 Aug 2009 3:14 AM #5
Here are some questions:
- Configuration - what format should the CPAN module accept?
- Class instantiation - do we need to bother? I have been calling the methods directly.
- What target - CGI, CGI via simple Module, Apache modperl?
Mostly I am concentrating on the ModPerl implementation, as that is the one I am currently using, but I can easily abstract it.
24 Aug 2009 3:24 AM #6
24 Aug 2009 3:51 AM #7
What I mean is - configuration format. E.g. Config::Config, or Perl Data dump or JSON parsed. Because it is Apache we could use Apache format, but that tends to be a bit heavy weight.
I think the best approach right now is to complete the missing bits in simple - such as file upload.
24 Aug 2009 4:14 AM #8
25 Aug 2009 2:02 PM #9
26 Aug 2009 10:44 PM #10
New version released
New version released
New version released:
- simple CGI now supports Form posts
- modperl now supports loading config via Config::Any (Perl, JSON, YAML - you pick).
- modperl now support CGI form posts and returns (example also updated to show error on email)
- modperl now supports 'before' and 'after' method calls on each action and method - allows you to implement your own security, logging etc.
- modperl now "use CGI;" for form data