>Resent-Date: 20 Mar 2000 14:49:24 -0000
>Resent-Cc: recipient list not shown: ;
>Reply-To: <[EMAIL PROTECTED]>
>From: "Stephen Pair" <[EMAIL PROTECTED]>
>To: "Squeak" <[EMAIL PROTECTED]>
>Subject: [ENH] Squeak Server Pages (again)
>Date: Mon, 20 Mar 2000 09:57:36 -0500
>X-Priority: 3 (Normal)
>Importance: Normal
>Resent-From: [EMAIL PROTECTED]
>X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/17387
>X-Loop: [EMAIL PROTECTED]
>Resent-Sender: [EMAIL PROTECTED]
>
>The first post had some file-in problems.  This one should fix those.
>
>Once again, here is the preamble:
>
>--------------------------------------------------
>Change Set:            SSP (Squeak Server Pages)
>Date:                  17 March 2000
>Author:                        Stephen Pair
>
>This change set enables a servlet style methods to be written in the class
>browser.  I named it SSP because of it's likeness to JSP, PSP, etc.
>However, it's not exactly like those schemes, in that it has nothing
>(necessarily) to do with web serving and the like.  SSP methods write the
>contents of their source onto a stream.  Smalltalk code segments
>(delinieated with <? and ?>) can be embedded into this text.  These code
>segments should return a string (no conversion is performed by SSP).
>
>The following is an example:
>
>--- snip ---
>serveletExampleOn: strm
><ssp>
>
>This is an example servelet method.  I can embed code in this
>string as follows:  <? (1 + 1) printString ?>.
>
>--- snip ---
>
>To illustrate, this change set includes an example class, SSPPerson.
>Evaluate:
>
>       SSPPerson example
>
>and inspect the result.  Reading through the code, you will see the example
>ssp method.  SSP methods write their result onto a stream, which must be
>passed as the first argument to the method.  Streams are used to ensure the
>highest possible flexibility and speed.  Also, the <ssp> pragma indicates
>that the special SSPParser should be used instead of the regular parser.
>You must also have two carriage returns following the <ssp> pragma (to
>separate what is intended to be written onto the stream from the method
>header).
>
>Enjoy!
>Enjoy!
>Content-Type: application/octet-stream;
>       name="SSP.1.cs"
>Content-Disposition: attachment;
>       filename="SSP.1.cs"
>
>

%SSP.1.cs_1

SSP.1.cs_1

--------------------------
Mark Guzdial : Georgia Tech : College of Computing : Atlanta, GA 30332-0280
(404) 894-5618 : Fax (404) 894-0673 : [EMAIL PROTECTED]
http://www.cc.gatech.edu/gvu/people/Faculty/Mark.Guzdial.html

Reply via email to