Thomas Whitney wrote:
> Chris,
>
> Thanks for your prompt reply. A few more questions.
>
> I'm currently using AuthDBI for security on the sight. Can I use that
> database?
No, but it would be a piece of cake to migrate the data. OI uses
session-based authentication with cookies rather than HTTP
authentication.
> I'm using Apaceh::Session for session stuff and mySQL for the database.
> Overall I guess I wondering on the learning curve of OI and the porting from
> my current site to OI. Will I have to port everything to use it? One last
> question. Does OI impose much overhead on the system?
Since OI uses standard Perl modules for many of the pieces --
session handling uses Apache::Session, view processing uses the
Template Toolkit, parameter parsing (etc.) uses Apache::Request,
etc. -- the only porting for those pieces should be simple,
assuming that you've kept them fairly separate.
Porting your business logic (or whatever you'd like to call it)
will be more of an effort. How much depends on the degree you've
separated your tasks out already. So if you have a single method
that does all create/update/delete actions for a single record,
you will have quite a bit of work. But if you're using the same
sort of paradigm that CGI::Application uses, it shouldn't be
difficult at all.
As for the load: to my knowledge Andreas Nolte and his crew have
built the largest and most used system based on OI. If he says
it scales well, I tend to believe him :-) What's useful is that
all the helpful hints in the mod_perl guide are directly
applicable, and OI comes out of the box configured to use the
dual-server proxy setup the guide recommends.
Good luck!
Chris
--
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.
|
