Mailing List Archive: Discuss: Embperl vs mod

Discuss: Embperl vs mod_perl handler techniques?

Feb 28, 2000, 4:47 PM

Post #1 of 3 (1056 views)

I have not seen a discussion regarding the merits of an Embperl approach
to web application development vs. a mod_perl handler solution to the
same problem.

I see Embperl as a further abstraction of dynamic content generation by
allowing the logic to be placed directly into a file that is evaluated
on the fly, whereas mod_perl logic is written in the shape of a handler
that can be inserted in one of many stages of server and client
negotiation. This allows more complete page development without the
need of handler modification. True?

I also see Embperl as taking care of several aspects of session
management that otherwise would need to be developed if using the
mod_perl handler approach. True?

If a handler approach to site data and web application development is
already being used, is it best to stay the course, or would introducing
Embperl into such a site have a direct benefit?

I'm attempting to determine the benefits/drawbacks of Empberl
vs. mod_perl handler development for an intranet time keeping
application currently under development. I already have custom handlers
managing much of the data, and wish to know if Embperl brings anything
to the table that could benefit me in dynamic data manipulation,
particularly in the areas of database access (CRUD) as well as in
interface characteristics, such as dynamic lists and data pesistence.

Comments welcome.

Peace.

Re: Discuss: Embperl vs mod_perl handler techniques? [ In reply to ]

cliff at genwax

Feb 28, 2000, 6:01 PM

Post #2 of 3 (976 views)

Permalink

I am using it at our place and second all that was said here.
You can still use handlers in conjunction with it when necessary.

cliff rayman
genwax.com

Aaron Johnson wrote:

> Bruce,
>
> Embperl offers a rich feature set that eases the creation of lists, form
> elements, tables, and a hrefs that contain a query string, just to name a
> few.
>
> Embperl provides for excellent form handling. The @ffld and %fdat contain
> all your form data. The @ffld is in the order of the preceding pages form
> elements so you can pop or shift the hidden fields that contained the "pass
> through" data and then use the array for database inserts and updates very
> easily.
>
> Sessions are handled in conjunction with the Apache::Session module, but
> creation and destruction is handled by Embperl. All that is required of the
> developer is to create a key for %udat and the session is created.
> Apache::Session allows for storage of the Session information in memory,
> flat file, or SQL database.
>
> Embperl has excellent error and debugging control as well.
>
> I have written modules that augment the features of Embperl to handle my
> redundant tasks and have found it very "friendly" to work with. I find
> Embperl in conjunction with Apache::Session a very power combination.
>
> Thank you Jeffrey Baker and Gerald Richter for these two excellent modules.
>
> my $.02
>
> Aaron Johnson
>
> "Bruce W. Hoylman" wrote:
>
> > I have not seen a discussion regarding the merits of an Embperl approach
> > to web application development vs. a mod_perl handler solution to the
> > same problem.
> >
> > I see Embperl as a further abstraction of dynamic content generation by
> > allowing the logic to be placed directly into a file that is evaluated
> > on the fly, whereas mod_perl logic is written in the shape of a handler
> > that can be inserted in one of many stages of server and client
> > negotiation. This allows more complete page development without the
> > need of handler modification. True?
> >
> > I also see Embperl as taking care of several aspects of session
> > management that otherwise would need to be developed if using the
> > mod_perl handler approach. True?
> >
> > If a handler approach to site data and web application development is
> > already being used, is it best to stay the course, or would introducing
> > Embperl into such a site have a direct benefit?
> >
> > I'm attempting to determine the benefits/drawbacks of Empberl
> > vs. mod_perl handler development for an intranet time keeping
> > application currently under development. I already have custom handlers
> > managing much of the data, and wish to know if Embperl brings anything
> > to the table that could benefit me in dynamic data manipulation,
> > particularly in the areas of database access (CRUD) as well as in
> > interface characteristics, such as dynamic lists and data pesistence.
> >
> > Comments welcome.
> >
> > Peace.

Re: Discuss: Embperl vs mod_perl handler techniques? [ In reply to ]

solution at gina

Feb 28, 2000, 6:07 PM

Post #3 of 3 (1005 views)

Permalink

Bruce,

Embperl offers a rich feature set that eases the creation of lists, form
elements, tables, and a hrefs that contain a query string, just to name a
few.

Embperl provides for excellent form handling. The @ffld and %fdat contain
all your form data. The @ffld is in the order of the preceding pages form
elements so you can pop or shift the hidden fields that contained the "pass
through" data and then use the array for database inserts and updates very
easily.

Sessions are handled in conjunction with the Apache::Session module, but
creation and destruction is handled by Embperl. All that is required of the
developer is to create a key for %udat and the session is created.
Apache::Session allows for storage of the Session information in memory,
flat file, or SQL database.

Embperl has excellent error and debugging control as well.

I have written modules that augment the features of Embperl to handle my
redundant tasks and have found it very "friendly" to work with. I find
Embperl in conjunction with Apache::Session a very power combination.

Thank you Jeffrey Baker and Gerald Richter for these two excellent modules.

my $.02

Aaron Johnson

"Bruce W. Hoylman" wrote:

> I have not seen a discussion regarding the merits of an Embperl approach
> to web application development vs. a mod_perl handler solution to the
> same problem.
>
> I see Embperl as a further abstraction of dynamic content generation by
> allowing the logic to be placed directly into a file that is evaluated
> on the fly, whereas mod_perl logic is written in the shape of a handler
> that can be inserted in one of many stages of server and client
> negotiation. This allows more complete page development without the
> need of handler modification. True?
>
> I also see Embperl as taking care of several aspects of session
> management that otherwise would need to be developed if using the
> mod_perl handler approach. True?
>
> If a handler approach to site data and web application development is
> already being used, is it best to stay the course, or would introducing
> Embperl into such a site have a direct benefit?
>
> I'm attempting to determine the benefits/drawbacks of Empberl
> vs. mod_perl handler development for an intranet time keeping
> application currently under development. I already have custom handlers
> managing much of the data, and wish to know if Embperl brings anything
> to the table that could benefit me in dynamic data manipulation,
> particularly in the areas of database access (CRUD) as well as in
> interface characteristics, such as dynamic lists and data pesistence.
>
> Comments welcome.
>
> Peace.