[Aspinfinity-developer] (no subject)

[Matt <mat...@ya...>]

While searching through the great and mighty WWW for an example of OOD for
any members not total familiar with the idea I came across two rather yummy
articles.

First the tutorial/intro: http://juicystudio.com/tutorial/asp/classes.asp

Now for those articles.  They deal with uploading and calendar two things
which may well need to become first level functions /apps that are available
to developers from the beginning.  This means creating API effectively to
interact with the class level of things.

I would like to challenge some people to create draft proposals of the
examples given and work them into applications for the ASP infinity project
despite the fact that infinity does not technically do anything yet.
Where-ever a call is outside the scope of the app a note should be made of
the requirement so that we create a form of road map towards a proper RC for
Asp Infinity.

This rises a few questions.  If Calendar is an application then it must use
the Database-Class however if it core tech exposing API for developers then
should it interface directly with the DB?  Where does pure Object design
give way to speed and so forth.

Further questions are raised which should be addressed and these include
what is core and what is application?  Where, if at all, do we draw the
line?  What data structure should an intrinsic calendar system use?  should
upload be a core function and what should it do (if anything) with it's
data?  What should the designated default folder be for such things and how
does that effect the whole design?  How should defaults be handled anyway?

Now I've opened a can of debate up here are the two articles begging to
become part of our project:

http://www.asp101.com/articles/jacob/calendar/default.asp
http://www.asp101.com/articles/jacob/scriptupload.asp

-Matt

A)bort, R)etry, I)nfluence with large hammer.

PS.  It seems that my system has refused to send this mail (I did wonder
what had happened).  I'm sending again now.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.3 - Release Date: 15/03/2005