Using sub-routines in ASP

Ello,

I'm trying to code my apps like I would a program using OOP's seperating the logic from presentation.

Since ASP is a scripting language how far should you go in spliting up the operations into sub-routines.

I'm initially considering using it for user management (authentication, session, etc)

Normally I just put the code where I need the effect but when it comes to alterations it is time consuming.

Are there any guidelines I should follow or best practices which would help in this implementation.

Thanks


--------------------------------------------------------------
So much trouble in the World - Bob Marley
------------------------------------------------------------

Me Again,

Is it better to do them using Jscript or Vbscript my question sounds dumb but i'm not sure if they both work without problems
(interacting with each other that is)



----------------------------------------------------------------------------
Knowledge = Call ForumHelp(status 'begging', matter 'urgent' )

i.e get the idea
---------------------------------------------------------------------------

Wow, you must not have too big of programs if you aren't using Functions/Subs. Otherwise I bet you have a bunch of code in If statements. Actually, using Functions and Subs isn't really OO, but using Classes is. Each class should have a specific intention and all of its functions and subs will be the methods needed for that class.

For instance, I have a database class that has Functions (they return true/false based on success in completion) to handle various DB tasks such has open connection, open recordset, execute SQL, close recordset, and close connection.

When getting down to object oriented programming though, classic ASP nor PHP really fully fit the bill like Java/C++ do. True OO would involve using classes with subclasses with subclasses, etc.., and ASP & PHP only support 1 class level. Sure you can open classes within classes, but each class is a local object and it is not possible to traverse up/down the class tree.

If you wanna properly separate your business logic and presentation, your can code some DLL's (called COM objects). You can write these in a few language, usually people use VB or C++. Writing COM's will greatly increase your app's performance.

I'm with wes, how on earth have you survived without functions/subs?!

PS - you can write classes in ASP, but they're not really proper classes.

Ello again,

I actually do use them but my problem is how far can I go with them.

I'm used to JSP with beans, etc, so normally I seperate every blessed thing from presentation. Transfering now to ASP and trying out a few things.

Cause the examples you normally find on the net do everything on the page. I wondered if it was a common practice.
If you know of any site that deals with structuring ASP send the link


Thanks again I go split this crap now

Yeah - the ASP language tends to promote sloppy coding. It doesn't exactly make it easy to seperate your business/pres logics.

Try not to get into the habbit of putting the code in the HTML. It's bad because if you want to change the site, it's not the simple act of changing your HTML templates.

Placing your subs/functions in 'include' files is generally idea, as is coding up COM's for larger sites. If you wanna know more, feel free to ICQ me.