openinteract-dev Mailing List for OpenInteract (Page 15)

Brought to you by: a_v, lachoy, mjbaker

openinteract-dev — For OI developers, includes project coordination and technical discussion.

You can subscribe to this list here.

2001	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (19)	Nov (22)	Dec (19)
2002	Jan (35)	Feb (5)	Mar (13)	Apr (9)	May (3)	Jun (16)	Jul	Aug (6)	Sep (15)	Oct (5)	Nov (3)	Dec (7)
2003	Jan (16)	Feb (10)	Mar (19)	Apr (13)	May (5)	Jun (20)	Jul (33)	Aug (9)	Sep (1)	Oct (12)	Nov (17)	Dec (2)
2004	Jan (3)	Feb (9)	Mar (7)	Apr (16)	May (6)	Jun (6)	Jul (18)	Aug (8)	Sep (27)	Oct (8)	Nov (14)	Dec (29)
2005	Jan (1)	Feb (11)	Mar (33)	Apr (2)	May (4)	Jun (21)	Jul (41)	Aug (6)	Sep	Oct (1)	Nov	Dec (1)
2006	Jan (8)	Feb (3)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec

Flat | Threaded

<< < 1 .. 13 14 15 16 17 .. 25 > >> (Page 15 of 25)

Re: [Openinteract-dev] Random tidbits on OI2

From: Chris W. <ch...@cw...> - 2003-07-08 02:26:09

Greg Fenton wrote:
> This is not my experience (using OpenInteract-1.99_01):

Sorry, I should have prefaced that with: "I just committed a change 
to CVS that did foo..." and/or "It'll be in the next version" :-)

C

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.

[Openinteract-dev] Question about Page

From: Greg F. <gre...@ya...> - 2003-07-08 02:04:18

Maybe I'm missing the docs, but I have created a new HTML page that I'd
like to serve.  I placed it in $OPENINTERACT2/html and now try to
create the page with OI2's "Page Actions" link.

Every time I fill out the create form, I get back the error:

  No template found in 'c_display_add_template' key. This template is
  mandatory for the task to function.

Problem is, I'm not exactly sure what a valid "template" is.  I have
tried various values I see when I list templates (base_simple,
base_main, page_displayable, etc...) but I always get the above error. 
I tried to create a new template, but got another error (see "Re:
Random tidbits on OI2" email earlier in this list).

So, what are the steps to getting an existing HTML file served?  Am I
missing a key manual page somewhere?

Thanks in advance,
greg_fenton.

=====
Greg Fenton
gre...@ya...

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Openinteract-dev] Re: Random tidbits on OI2

From: Greg F. <gre...@ya...> - 2003-07-08 01:54:57

Even more simple tidbits.  Again, I'm using OpenInteract-1.99_01:

A. I created website as per QuickStart.  When I go to "System
   Documentation" and click the SPOPS::Manual link, all is fine.
   When I click the OpenInteract2::Manual link, I get the error page:

   Can't call method "present" without a package or object reference
   at /usr/lib/perl5/site_perl/5.8.0/Pod/POM/View/Pod.pm line 132.


B. In base_page-2.05/doc/base_page.pod, line 129 gives an example
   using "oi_manage" and not "oi2_manage".


C. From the homepage of the QuickStart website, I click "Pages" (top
   of the page), then expand the root directory, then click on the
   "index.html" link.  I get the error:

   Cannot find valid method in [OpenInteract2::Action::Page] for
   task [show]


D. From the homepage of the QuickStart website, I click on the 
   "Template (New)" link and get the following error:

   Cannot find valid method in [OpenInteract2::Action::SiteTemplate]
   for task [display] 


Hope this helps,
greg_fenton.



=====
Greg Fenton
gre...@ya...

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

Re: [Openinteract-dev] Random tidbits on OI2

From: Greg F. <gre...@ya...> - 2003-07-08 00:19:27

--- Chris Winters <ch...@cw...> wrote:
> 
> One note: in oi2_daemon you still can't choose where the PID file 
> goes, but it always goes in the directory from where the daemon 
> configuration is read (normally WEBSITE_DIR/conf) so at least it's 
> consistent.
> 

Chris,

This is not my experience (using OpenInteract-1.99_01):

  $ mkdir foo
  $ cd foo
  $ ls
  $
  $ export OPENINTERACT2=/home/greg/dev/oi2/website
  $ oi2_daemon
  Using OPENINTERACT2 environment for website directory:
    /home/greg/dev/oi2/website
  Using daemon configuration from website directory
  OpenInteract2 now running at URL <http://<my_hostname>:8080/>
  $ ls
  daemon.log  oi2.pid
  $


Hope this helps,
greg_fenton.

=====
Greg Fenton
gre...@ya...

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

Re: [Openinteract-dev] Testnotes with OI2Beta01

From: Chris W. <ch...@cw...> - 2003-07-07 19:17:21

Andreas Nolte wrote:
> 1) Upgrade test beta00 -> beta01
> - copied missing log4perl.conf and replaces [% website_dir %]
> - oi2_manage upgrade --website_dir=/data/oi/oi2test/
 > ...
> [oi2_manage]: Caught exception during task execution.
> Can't locate object method "new" via package
> "OpenInteract::Config::TransferSample" (perhaps you forgot to load
> "OpenInteract::Config::TransferSample"?) at
> /usr/lib/perl5/site_perl/5.8.0/OpenInteract2/Manage/Website/Upgrade.pm
> line 47, <CONF> line 135.

Whoops! Haven't tested this yet... it looks like it only bailed on 
the last step, copying the sitewide templates over. It's fixed in CVS.

> -> I chose to ignore this for now
> -> started website with mysql/lwp
> -> startup ok
> -> when request comes in: 
> New client attached from: 127.0.0.1
> Cannot process template [base_main]: Undefined subroutine
> &Template::Parser::new_style called at
> /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Template/Parser.pm line 179.
> daemon: Reaped child with PID [1]

This is a *weird* TT error. What's strange is that in my TT version 
  (2.09) 'new_style' is defined about 10 lines under where this 
error was thrown. And OI doesn't have anything to do with TT parsers 
(plugins, providers and contexts, yes, but no parsers).

What TT version are you using?

> 2) Fresh install
> - oi2_manage create_website runs w/o a problem
> - used server.ini with lwp and a MySQL DB
> - did install_sql --package=SYSTEM -> OK
> - tried to start the daemon -> not OK 
> - here the tail of oi2.log:
> 20:28:56 INFO OI2.REQUEST OpenInteract2::Request (309) Loaded theme 1
> ok, getting values
> 20:28:57 ERROR OI2.ACTION OpenInteract2::Controller (146) Cannot create
> controller [main] -- Failure to get factory class for [main]: Factory
> type [main] is not defined in [OpenInteract2::Controller]

You'll need to change your server config. Sorry about not mentioning 
this in the changelog (future betas will have much more detailed logs).

You should have the following entries in the 'content_generator' and 
'controller' sections:

========================================
#
# Define the different content generators...

[content_generator]
default  = TT

[content_generator TT]
class    = OpenInteract2::ContentGenerator::TT2Process
method   = process

# Sample for Text::Template
#[content_generator TextTmpl]
#class    = OpenInteract2::ContentGenerator::TextTemplate
#method   = process

# Sample for HTML::Template
#[content_generator HTMLT]
#class    = OpenInteract2::ContentGenerator::HtmlTemplate
#method   = process

#
# Define the main controller...

[controller tt-template]
content_generator = TT
class             = OpenInteract2::Controller::MainTemplate

[controller html-template]
content_generator = HTMLT
class             = OpenInteract2::Controller::MainTemplate

[controller text-template]
content_generator = TextTmpl
class             = OpenInteract2::Controller::MainTemplate

[controller raw]
class             = OpenInteract2::Controller::Raw

# The action table defines ...

[action_info default]
controller         = tt-template
content_generator  = TT

========================================

Thanks for the report!

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.

[Openinteract-dev] Testnotes with OI2Beta01

From: Andreas N. <an...@kl...> - 2003-07-07 18:33:44

Hey y'all,

here my - admittedly short - tests of OI2Beta01:

0) compilation: no problems inkl. make test 

1) Upgrade test beta00 -> beta01
- copied missing log4perl.conf and replaces [% website_dir %]
- oi2_manage upgrade --website_dir=/data/oi/oi2test/

PROGRESS: Starting task
PROGRESS: Upgrading packages
 ... this may take a while ...
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/base-2.03.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/base_box-2.02.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/base_error-2.04.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/base_group-2.02.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/base_page-2.05.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/base_security-2.02.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/base_template-3.02.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/base_theme-2.02.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/base_user-2.04.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/full_text-2.03.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/news-2.03.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/lookup-2.01.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/object_activity-2.03.zip
PROGRESS: Task complete
PROGRESS: Starting task
PROGRESS: Finished with installation of
/usr/src/OpenInteract-1.99_01/pkg/system_doc-2.01.zip
PROGRESS: Task complete
PROGRESS: Package upgrade complete
Caught error: Can't locate object method "new" via package
"OpenInteract::Config::TransferSample" (perhaps you forgot to load
"OpenInteract::Config::TransferSample"?) at
/usr/lib/perl5/site_perl/5.8.0/OpenInteract2/Manage/Website/Upgrade.pm
line 47, <CONF> line 135.
 at /usr/bin/oi2_manage line 197
[oi2_manage]: Caught exception during task execution.
Can't locate object method "new" via package
"OpenInteract::Config::TransferSample" (perhaps you forgot to load
"OpenInteract::Config::TransferSample"?) at
/usr/lib/perl5/site_perl/5.8.0/OpenInteract2/Manage/Website/Upgrade.pm
line 47, <CONF> line 135.

-> I chose to ignore this for now
-> started website with mysql/lwp
-> startup ok
-> when request comes in: 
New client attached from: 127.0.0.1
Cannot process template [base_main]: Undefined subroutine
&Template::Parser::new_style called at
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Template/Parser.pm line 179.
daemon: Reaped child with PID [1]

- stopped here -

2) Fresh install
- oi2_manage create_website runs w/o a problem
- used server.ini with lwp and a MySQL DB
- did install_sql --package=SYSTEM -> OK
- tried to start the daemon -> not OK 
- here the tail of oi2.log:
20:28:56 INFO OI2.REQUEST OpenInteract2::Request (309) Loaded theme 1
ok, getting values
20:28:57 ERROR OI2.ACTION OpenInteract2::Controller (146) Cannot create
controller [main] -- Failure to get factory class for [main]: Factory
type [main] is not defined in [OpenInteract2::Controller]

20:28:57 INFO OI2.RESPONSE OpenInteract2::Response::LWP (37) Sending LWP
response
20:28:57 INFO OI2.RESPONSE OpenInteract2::Response::LWP (42) Saved
session ok
20:28:57 FATAL OI2 Log::Log4perl::Logger (740) Caught error from
response: Not a SCALAR reference at
/usr/lib/perl5/site_perl/5.8.0/OpenInteract2/Response/LWP.pm line 62.

20:28:57 FATAL OI2 Log::Log4perl::Logger (740)  at /usr/bin/oi2_daemon
line 161

20:28:57 INFO OI2 main (219) Reaped child with PID [1]


- stopped here -

I` ll try to find some time to find out what this is, but hints a surely
appreciated..

later,

Andreas

Re: [Openinteract-dev] Random tidbits on OI2

From: Chris W. <ch...@cw...> - 2003-07-07 17:59:12

Greg Fenton wrote:
> More simple tidbits:
>  ...

All great suggestions, all implemented except one. The one that 
wasn't had to do with the HTML rendering of the intradocument link. 
For that I need to fix the Pod::POM renderer and that will take a 
few more minutes than I have today.

One note: in oi2_daemon you still can't choose where the PID file 
goes, but it always goes in the directory from where the daemon 
configuration is read (normally WEBSITE_DIR/conf) so at least it's 
consistent.

Thanks for the detailed report!

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.

[Openinteract-dev] Random tidbits on OI2

From: Greg F. <gre...@ya...> - 2003-07-07 02:46:21

More simple tidbits:

1. OpenInteract2::Manual::Intro, last sentence of "Controller"
   description says "... from once place."  (should be "from one
   place.")

2. In OpenInteract2::Manual::QuickStart, the first bullet under
   "Prerequisites" states "This is the normal four-step installation
   process...".  It would be nice to have a link to the normal process.

3. In OpenInteract2::Manual::QuickStart, the last bullet under
   "Prerequisites" has a link to "SEE ALSO", but it doesn't work.
   That HREF is to "#" but should be to "#SEE_ALSO".

4. In OpenInteract2::Manual::QuickStart, it should be explicitly stated
   that LWP is being used as the webserver.  This should probably be
   stated before or at the very beginning of "Creating A Website".  I
   found myself wondering if/how I was going to set up Apache without
   affecting my existing website.

5. In OpenInteract2::Manual::QuickStart, it says that the daemon can
   be killed by kill -15 `cat oi2.pid`, but nowhere did we state where
   oi2.pid is created (in $PWD when oi2_daemon is run).  If there is a
   way to specify where the PID file can go, this should be indicated.
   If there isn't, then there should be :-)

6. Now that I have my very own OI2 running (the QuickStart, running
with
   LWP and SQLite), I login as superuser and go to "Object Activity". 
I
   set "Activity By" to superuser and click "Search".  The resulting
   table shows dates of "DateTime=HASH(0x891d9c4)" instead of the
actual
   date/time.

7. In OpenInteract2::Manual::Architecture, Step 0 of TRACING A REQUEST
   says "[The adapter] will run a number of processes at server
startup"
   I don't believe that a number of "processes" run, but that a bunch
   of "tasks" or "jobs" are performed.  Since its talking about the
   startup of a server, the phrase "process" might make a developer
   or administrator leary of OI2.

8. In OpenInteract2::Manual::Architecture, Step 6 of TRACING A REQUEST
   is missing the first letter of the very first word ("he" instead of
   "The").

9. In OpenInteract2::Manual::Architecture, Step 7 of TRACING A REQUEST
   the logic of the section is backwards.  It starts off with "Find out
   if the task is invalid", but then lists points of validity (not
   invalidity).  Also, the very last point is vague (*what* is
   listed there?).

Hope this helps,
greg_fenton.

=====
Greg Fenton
gre...@ya...

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

Re: [Openinteract-dev] OI 2 testing

From: Chris W. <ch...@cw...> - 2003-06-23 20:01:21

Andreas Nolte wrote:
> the tip with for the thread problem (
> OpenInteract2::DatasourceManager->shutdown; )
> seams to work ! Now it` s up to porting the Request/Response methods.
> I`ll take the approach to use the mp2 api where available and use some
> std. module for the rest ( cookies, uploads etc ) and not
> libapreq-2-alpha .

Great! One source of info might be the OpenFrame project. I swiped 
some of the other Request implementations from them (with a nod of 
the head, of course) and IIRC Leon create at least a prelim 
implementation for Apache2.

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.

Re: [Openinteract-dev] OI 2 testing

From: Andreas N. <an...@kl...> - 2003-06-23 19:50:00

Hi Chris,

the tip with for the thread problem (
OpenInteract2::DatasourceManager->shutdown; )
seams to work ! Now it` s up to porting the Request/Response methods.
I`ll take the approach to use the mp2 api where available and use some
std. module for the rest ( cookies, uploads etc ) and not
libapreq-2-alpha .

regards,

Andreas


On Mon, 2003-06-23 at 08:09, Chris Winters wrote:
> Andreas Nolte wrote:
> > finally found the time to do some OI 2 / Beta 0 testing.
> >
> > First impression in short: already works great.
> 
> This is extremely valuable. Thanks a ton for taking the time.
> 
> > After this I followed the readme / Manual::Intro and setup a testing
> > site with lwp. This all worked by the book !
> 
> Cool!
> 
> > The only spottable "error" I found in the news package: here the display
> > of dates is not correct in the templates. It shows the class name, so I
> > assume a deref is missing somewhere.
> 
> I'll check into this. All date fields in core packages are converted 
> automatically to DateTime objects....
> 
> > Switching on debugging als shows, that OI 2 is whining about a few
> > classes not specifying a "date conversion format". These are classes
> > News, ErrorObject, Page, User and ObjectAction.
> 
> ...which is why this was complaining. I'll probably just put the 
> universal 'yyyy-mm-dd hh:mm:ss' in for this: I think any database 
> should be able to handle it.
> 
> > Next I tested with apache 1.3.26 / mod_perl 1.27 by switching the types
> > in the configs. I was interested, if this would do any harm to the site
> > or change anything in the layout - no - works w/o a problem.
> 
> hooray!
> 
> > Now I switched the DBI type from SQLite to Mysql 4.0.13, reinstalled the
> > SQL etc -> success. 
> 
> Even better -- I'd only tested with PostgreSQL (7.3 something) and 
> SQLite.
> 
> > Since this all worked to easy so far ;-), I tried to go for
> > Apache2/mod_perl2 by registering a new factory type for the
> > request/response classes and setting up an Apache2::OpenInteract2
> > handler class. Basically, it turns out to be a rather small task with
> > the main "problem" being, that the mod_perl2 documentation is not ready
> > yet. 
> 
> You're very optimistic :-)
> 
> > BTW: could anyone tell me where $REQUEST_CLASS is set in Request.pm and
> > where the get_current method in Request/Apache.pm comes from ?
> 
> During setup OI2::Context->assign_request_type() (and 
> assign_response_type() for Response.pm) calls 
> OI2::Request->set_implementation_type() with the relevant type name. 
> The type name is read from the server.ini file, although you can set 
> it afterward too.
> 
> > I fell across s.th. different, though: treads and databases !
> > Since mod_perl2 works with ithreads ( meaning one perl instance in every
> > thread), which means, a shared nothing aproach is used, I did not see
> > reason for not trying the treaded worker mpm. 
> > The problem is, that in perl 5.8.0 you cannot share any object across
> > threads, so also no db connections. This also means, that you cannot use
> > any db object from the initial thread in any other thread.
> > Here I fell with OI2, since the db connections are made quite early,
> > before the initial thread is cloned to handle the request.
>  > ...
>  > Is there a chance to kick the connections and reestablish them
>  > in them when the request is handled? At that point, you could do
>  > caching of db connections, since you are within a separate thread.
> 
> I had to deal with this in the LWP daemon too. Before we do the fork 
> we execute the following:
> 
>      # We need to close all database handle created in the
>      # initialization process so the child doesn't try to use it.
>      OpenInteract2::DatasourceManager->shutdown;
> 
> In theory this would work with mp2 as well -- you'd probably execute 
> this as the last line in the startup.pl.
> 
> After seeing Artur's presentation on threads at YAPC::NA I'm curious 
> to see what other changes are necessary. I'm in the process of 
> modifying OI2::Context so that certain configuration items (action 
> table, SPOPS config info, ...) are accessed by methods alone... This 
> will make it easier to follow what's going on and also provide the 
> means to use threads::shared to share what little read/write data 
> exists in the CTX object.
> 
> > Also I tried to read a bit through the OI2 code and find it a lot more
> > understandable than the OI1 code. I especially like the use of
> > Class::Accessor and Class::Factory and the CTX singleton.
> 
> Yeah -- there shouldn't be anymore magical hashref accesses :-)
> 
> > Looking at the new News package, I found it not too different from the
> > OI1 packages, which is great because it means that porting modules
> > should not hurt too much.
> 
> It really shouldn't be too bad -- most everything is:
> 
>    - changing $R data access/methods to CTX/request/response
>    - accessing action state using ->param(...) rather than passing 
> around \%p
>    - calling 'generate_content()' on the action itself and passing 
> only parameter and template identifier info
>    - if you're using OI::CommonHandler you'll need to move most/all 
> of the declarations into the action configuration, change some 
> method names (e.g., 'show' becomes 'display', 'display_form' and 
> 'display_add'; 'edit' becomes 'update' and 'add', etc.) and modify 
> what you inherit from
> 
> > The verbose feedback of oi2_manage is also a good idea.
> 
> I think I'm going to move most of the functionality from oi2_manage 
> into a class so packages can declare tasks at runtime and allow 
> addtional parameters to be passed in... we'll see. It's MUCH easier 
> now to add tasks, report info, etc.
> 
> > In short: first impression is really great - well done Chris !
> 
> Thanks! The real test comes when you try to port NATS and other 
> modules :-)
> 
> Chris

AW: [Openinteract-dev] OI 2 testing

From: <And...@Be...> - 2003-06-23 07:24:47

.. Actually Dietmar and I already talked about this. Since most =
dependencies
are more towards SPOPS and the NATS framework runs w/o OI anyway it =
won`t be
a problem. I hope we can release a "public beta" of the nats framework
together will NATS-Ticket as a sample application soon. Most left to do =
is
docs and making it installable ;-)

-----Urspr=FCngliche Nachricht-----
Von: Chris Winters [mailto:ch...@cw...]=20
Gesendet: Montag, 23. Juni 2003 08:09
An: Andreas Nolte
Cc: ope...@li...
Betreff: Re: [Openinteract-dev] OI 2 testing

Andreas Nolte wrote:
> finally found the time to do some OI 2 / Beta 0 testing.
>
> First impression in short: already works great.

This is extremely valuable. Thanks a ton for taking the time.

> After this I followed the readme / Manual::Intro and setup a testing=20
> site with lwp. This all worked by the book !

Cool!

> The only spottable "error" I found in the news package: here the=20
> display of dates is not correct in the templates. It shows the class=20
> name, so I assume a deref is missing somewhere.

I'll check into this. All date fields in core packages are converted=20
automatically to DateTime objects....

> Switching on debugging als shows, that OI 2 is whining about a few=20
> classes not specifying a "date conversion format". These are classes=20
> News, ErrorObject, Page, User and ObjectAction.

...which is why this was complaining. I'll probably just put the=20
universal 'yyyy-mm-dd hh:mm:ss' in for this: I think any database=20
should be able to handle it.

> Next I tested with apache 1.3.26 / mod_perl 1.27 by switching the=20
> types in the configs. I was interested, if this would do any harm to=20
> the site or change anything in the layout - no - works w/o a problem.

hooray!

> Now I switched the DBI type from SQLite to Mysql 4.0.13, reinstalled=20
> the SQL etc -> success.

Even better -- I'd only tested with PostgreSQL (7.3 something) and=20
SQLite.

> Since this all worked to easy so far ;-), I tried to go for=20
> Apache2/mod_perl2 by registering a new factory type for the=20
> request/response classes and setting up an Apache2::OpenInteract2=20
> handler class. Basically, it turns out to be a rather small task with =

> the main "problem" being, that the mod_perl2 documentation is not=20
> ready yet.

You're very optimistic :-)

> BTW: could anyone tell me where $REQUEST_CLASS is set in Request.pm=20
> and where the get_current method in Request/Apache.pm comes from ?

During setup OI2::Context->assign_request_type() (and=20
assign_response_type() for Response.pm) calls=20
OI2::Request->set_implementation_type() with the relevant type name.=20
The type name is read from the server.ini file, although you can set=20
it afterward too.

> I fell across s.th. different, though: treads and databases ! Since=20
> mod_perl2 works with ithreads ( meaning one perl instance in every=20
> thread), which means, a shared nothing aproach is used, I did not see =

> reason for not trying the treaded worker mpm. The problem is, that in =

> perl 5.8.0 you cannot share any object across threads, so also no db=20
> connections. This also means, that you cannot use any db object from=20
> the initial thread in any other thread. Here I fell with OI2, since=20
> the db connections are made quite early, before the initial thread is =

> cloned to handle the request.
 > ...
 > Is there a chance to kick the connections and reestablish them  > in =
them
when the request is handled? At that point, you could do  > caching of =
db
connections, since you are within a separate thread.

I had to deal with this in the LWP daemon too. Before we do the fork=20
we execute the following:

     # We need to close all database handle created in the
     # initialization process so the child doesn't try to use it.
     OpenInteract2::DatasourceManager->shutdown;

In theory this would work with mp2 as well -- you'd probably execute=20
this as the last line in the startup.pl.

After seeing Artur's presentation on threads at YAPC::NA I'm curious=20
to see what other changes are necessary. I'm in the process of=20
modifying OI2::Context so that certain configuration items (action=20
table, SPOPS config info, ...) are accessed by methods alone... This=20
will make it easier to follow what's going on and also provide the=20
means to use threads::shared to share what little read/write data=20
exists in the CTX object.

> Also I tried to read a bit through the OI2 code and find it a lot =
more=20
> understandable than the OI1 code. I especially like the use of=20
> Class::Accessor and Class::Factory and the CTX singleton.

Yeah -- there shouldn't be anymore magical hashref accesses :-)

> Looking at the new News package, I found it not too different from =
the=20
> OI1 packages, which is great because it means that porting modules=20
> should not hurt too much.

It really shouldn't be too bad -- most everything is:

   - changing $R data access/methods to CTX/request/response
   - accessing action state using ->param(...) rather than passing=20
around \%p
   - calling 'generate_content()' on the action itself and passing=20
only parameter and template identifier info
   - if you're using OI::CommonHandler you'll need to move most/all=20
of the declarations into the action configuration, change some=20
method names (e.g., 'show' becomes 'display', 'display_form' and=20
'display_add'; 'edit' becomes 'update' and 'add', etc.) and modify=20
what you inherit from

> The verbose feedback of oi2_manage is also a good idea.

I think I'm going to move most of the functionality from oi2_manage=20
into a class so packages can declare tasks at runtime and allow=20
addtional parameters to be passed in... we'll see. It's MUCH easier=20
now to add tasks, report info, etc.

> In short: first impression is really great - well done Chris !

Thanks! The real test comes when you try to port NATS and other=20
modules :-)

Chris

--=20
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.

-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting =
Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly =
Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
openinteract-dev mailing list ope...@li...
https://lists.sourceforge.net/lists/listinfo/openinteract-dev

Re: [Openinteract-dev] OI 2 testing

From: Chris W. <ch...@cw...> - 2003-06-23 05:46:56

Andreas Nolte wrote:
> finally found the time to do some OI 2 / Beta 0 testing.
>
> First impression in short: already works great.

This is extremely valuable. Thanks a ton for taking the time.

> After this I followed the readme / Manual::Intro and setup a testing
> site with lwp. This all worked by the book !

Cool!

> The only spottable "error" I found in the news package: here the display
> of dates is not correct in the templates. It shows the class name, so I
> assume a deref is missing somewhere.

I'll check into this. All date fields in core packages are converted 
automatically to DateTime objects....

> Switching on debugging als shows, that OI 2 is whining about a few
> classes not specifying a "date conversion format". These are classes
> News, ErrorObject, Page, User and ObjectAction.

...which is why this was complaining. I'll probably just put the 
universal 'yyyy-mm-dd hh:mm:ss' in for this: I think any database 
should be able to handle it.

> Next I tested with apache 1.3.26 / mod_perl 1.27 by switching the types
> in the configs. I was interested, if this would do any harm to the site
> or change anything in the layout - no - works w/o a problem.

hooray!

> Now I switched the DBI type from SQLite to Mysql 4.0.13, reinstalled the
> SQL etc -> success. 

Even better -- I'd only tested with PostgreSQL (7.3 something) and 
SQLite.

> Since this all worked to easy so far ;-), I tried to go for
> Apache2/mod_perl2 by registering a new factory type for the
> request/response classes and setting up an Apache2::OpenInteract2
> handler class. Basically, it turns out to be a rather small task with
> the main "problem" being, that the mod_perl2 documentation is not ready
> yet. 

You're very optimistic :-)

> BTW: could anyone tell me where $REQUEST_CLASS is set in Request.pm and
> where the get_current method in Request/Apache.pm comes from ?

During setup OI2::Context->assign_request_type() (and 
assign_response_type() for Response.pm) calls 
OI2::Request->set_implementation_type() with the relevant type name. 
The type name is read from the server.ini file, although you can set 
it afterward too.

> I fell across s.th. different, though: treads and databases !
> Since mod_perl2 works with ithreads ( meaning one perl instance in every
> thread), which means, a shared nothing aproach is used, I did not see
> reason for not trying the treaded worker mpm. 
> The problem is, that in perl 5.8.0 you cannot share any object across
> threads, so also no db connections. This also means, that you cannot use
> any db object from the initial thread in any other thread.
> Here I fell with OI2, since the db connections are made quite early,
> before the initial thread is cloned to handle the request.
 > ...
 > Is there a chance to kick the connections and reestablish them
 > in them when the request is handled? At that point, you could do
 > caching of db connections, since you are within a separate thread.

I had to deal with this in the LWP daemon too. Before we do the fork 
we execute the following:

     # We need to close all database handle created in the
     # initialization process so the child doesn't try to use it.
     OpenInteract2::DatasourceManager->shutdown;

In theory this would work with mp2 as well -- you'd probably execute 
this as the last line in the startup.pl.

After seeing Artur's presentation on threads at YAPC::NA I'm curious 
to see what other changes are necessary. I'm in the process of 
modifying OI2::Context so that certain configuration items (action 
table, SPOPS config info, ...) are accessed by methods alone... This 
will make it easier to follow what's going on and also provide the 
means to use threads::shared to share what little read/write data 
exists in the CTX object.

> Also I tried to read a bit through the OI2 code and find it a lot more
> understandable than the OI1 code. I especially like the use of
> Class::Accessor and Class::Factory and the CTX singleton.

Yeah -- there shouldn't be anymore magical hashref accesses :-)

> Looking at the new News package, I found it not too different from the
> OI1 packages, which is great because it means that porting modules
> should not hurt too much.

It really shouldn't be too bad -- most everything is:

   - changing $R data access/methods to CTX/request/response
   - accessing action state using ->param(...) rather than passing 
around \%p
   - calling 'generate_content()' on the action itself and passing 
only parameter and template identifier info
   - if you're using OI::CommonHandler you'll need to move most/all 
of the declarations into the action configuration, change some 
method names (e.g., 'show' becomes 'display', 'display_form' and 
'display_add'; 'edit' becomes 'update' and 'add', etc.) and modify 
what you inherit from

> The verbose feedback of oi2_manage is also a good idea.

I think I'm going to move most of the functionality from oi2_manage 
into a class so packages can declare tasks at runtime and allow 
addtional parameters to be passed in... we'll see. It's MUCH easier 
now to add tasks, report info, etc.

> In short: first impression is really great - well done Chris !

Thanks! The real test comes when you try to port NATS and other 
modules :-)

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.

[Openinteract-dev] OI 2 testing

From: Andreas N. <an...@kl...> - 2003-06-22 12:06:17

Hey folks,

finally found the time to do some OI 2 / Beta 0 testing.

First impression in short: already works great.

Testenvironment was RedHat Linux 9, which includes a 5.8.0-ithread perl
version. During the installation, I only had the "usual" RH 9 and perl
problems comming from the new defaults for languages et. al ( e.g. UTF-8
charsets ), which lead to problems with quite a few perl moduels.

Apart from this, I only got an error during make test from the SQLite
module, which I chose to ignore.

After this I followed the readme / Manual::Intro and setup a testing
site with lwp. This all worked by the book !

The only spottable "error" I found in the news package: here the display
of dates is not correct in the templates. It shows the class name, so I
assume a deref is missing somewhere.

Switching on debugging als shows, that OI 2 is whining about a few
classes not specifying a "date conversion format". These are classes
News, ErrorObject, Page, User and ObjectAction.

Next I tested with apache 1.3.26 / mod_perl 1.27 by switching the types
in the configs. I was interested, if this would do any harm to the site
or change anything in the layout - no - works w/o a problem.

Now I switched the DBI type from SQLite to Mysql 4.0.13, reinstalled the
SQL etc -> success. 

Now back to LWP -> no problem.

Since this all worked to easy so far ;-), I tried to go for
Apache2/mod_perl2 by registering a new factory type for the
request/response classes and setting up an Apache2::OpenInteract2
handler class. Basically, it turns out to be a rather small task with
the main "problem" being, that the mod_perl2 documentation is not ready
yet. 

BTW: could anyone tell me where $REQUEST_CLASS is set in Request.pm and
where the get_current method in Request/Apache.pm comes from ?

I fell across s.th. different, though: treads and databases !
Since mod_perl2 works with ithreads ( meaning one perl instance in every
thread), which means, a shared nothing aproach is used, I did not see
reason for not trying the treaded worker mpm. 
The problem is, that in perl 5.8.0 you cannot share any object across
threads, so also no db connections. This also means, that you cannot use
any db object from the initial thread in any other thread.
Here I fell with OI2, since the db connections are made quite early,
before the initial thread is cloned to handle the request.

Probably, you would have the same problem with any other threaded
environment, as long as the db connections are setup in advance.

Is there a chance to kick the connections and reestablish them in them
when the request is handled? At that point, you could do caching of db
connections, since you are within a separate thread.


Also I tried to read a bit through the OI2 code and find it a lot more
understandable than the OI1 code. I especially like the use of
Class::Accessor and Class::Factory and the CTX singleton.
Looking at the new News package, I found it not too different from the
OI1 packages, which is great because it means that porting modules
should not hurt too much.
The verbose feedback of oi2_manage is also a good idea.

In short: first impression is really great - well done Chris !

regards,

Andreas

Re: [Openinteract-dev] can users set theme

From: Chris W. <ch...@cw...> - 2003-06-15 10:39:16

joseph speigle wrote:
> hello, I have started adding themes with data files run from
> SQLInstall.pm can users set their theme?  Is there any user
> configurable way to set theme -- like assigning the theme-number
> (1, 2 ..) to {default_objects}{theme} at user-login time or
> something like that.  Do you have any recommendations as to where
> to put this code in my package. I haven't upgraded yet, this is
> openinteract-1.57.

This used to be an option on the base_user::user_form template but 
for some reason I removed it.

To add it back in, you just need to add a new row something like this:

[%- count = count + 1 -%]
[% INCLUDE label_form_select_row( label       = 'Theme',
                                   name        = 'theme_id',
                                   picked      = user.theme_id,
                                   list        = theme_list,
                                   value_field = 'title',
                                   label_field => 'theme_id' ) -%]


And then add to the show() method OI/Handler/User.pm:

$params->{theme_list} = eval {
     $R->theme->fetch_group({ order => 'title' })
};


And then uncomment a few lines in the edit() method of 
OI/Handler/User.pm. They're marked already.

Good luck!

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.

[Openinteract-dev] can users set theme

From: joseph s. <joe...@jk...> - 2003-06-15 06:14:30

hello,
I have started adding themes with data files run from SQLInstall.pm
can users set their theme?  Is there any user configurable way to set theme -- like assigning the theme-number (1, 2 ..) to {default_objects}{theme} at user-login time or something like that.  Do you have any recommendations as to where to put this code in my package.
I haven't upgraded yet, this is openinteract-1.57.
thank you,
joe
-- 
joseph speigle
www.sirfsup.com
joe at jklh dot us
page: 377-7377 (210)

[Openinteract-dev] Re: SPOPS-0.77 buglet?

From: Chris W. <ch...@cw...> - 2003-06-10 20:32:03

Ray Zimmerman wrote:
> ... with SPOPS-0.77. Seems _w() is being called with $DEBUG undefined. I 
> noticed you typically do DEBUG() && _w(), but there are a few cases 
> where you don't check DEBUG() first. If I add the 'DEBUG() && ' to the 
> appropriate lines in SPOPS.pm, the problem goes away.

Yuck. Changing:

  my ( $DEBUG );

to:

  my $DEBUG = 0;

at the top of SPOPS.pm should also fix it. (Of course, using 
something like Log::Log4perl would REALLY fix it.) Sorry about that.

Later,

Chris

[Openinteract-dev] SPOPS-0.77 buglet?

From: Ray Z. <rz...@co...> - 2003-06-10 20:26:18

Hi Chris,

I found that my ESPOPS tests give me a bunch of errors like ...

Use of uninitialized value in numeric ge (>=) at 
/usr/local/perl-5.8.0/lib/site_perl/5.8.0/SPOPS.pm line 663, <SQL> 
line 100.
         SPOPS::_w(2,'No rules to process for [pre_fetch_action]') 
called at /usr/local/perl-5.8.0/lib/site_perl/5.8.0/SPOPS.pm line 332


... with SPOPS-0.77. Seems _w() is being called with $DEBUG 
undefined. I noticed you typically do DEBUG() && _w(), but there are 
a few cases where you don't check DEBUG() first. If I add the 
'DEBUG() && ' to the appropriate lines in SPOPS.pm, the problem goes 
away.

-- 
  Ray Zimmerman  / e-mail: rz...@co... / 428-B Phillips Hall
   Sr Research  /   phone: (607) 255-9645  /  Cornell University
    Associate  /      FAX: (815) 377-3932 /   Ithaca, NY  14853