Board index » delphi » Re: Will ISAPI continue?

2003-10-22 03:43:58 AM
delphi25
"Shawn Pfaff" <XXXX@XXXXX.COM>writes
to the request and response.
-Jimmy
 

On Tue, 21 Oct 2003 15:41:57 -0400, "Jimmy [Used-Disks]"
<XXXX@XXXXX.COM>writes:
Nick Hodges - TeamB
Lemanix Corporation
Please always follow the newsgroup guidelines --
www.borland.com/newsgroups
 

On Tue, 21 Oct 2003 15:43:58 -0400, "Jimmy [Used-Disks]"
<XXXX@XXXXX.COM>writes:
Nick Hodges - TeamB
Lemanix Corporation
Please always follow the newsgroup guidelines --
www.borland.com/newsgroups
 

control in the HTML because the Adapters don't put *anything* in the HTML.
At least in ASP.NET you can assign properties, for example:
<aspx:button text="Click Me" onclick="ClickTheButton"/>
WebBroker has the <#...>tags which are more flexible than WebSnap in terms
of generated HTML because they can take parameters. However, the HTML
generated is generated from compiled code - just as in ASP.NET. However,
ASP.NET allows you to nest tags and easily create much more complex controls
than in WebBroker. Also, since both technologies require compiled code to
process the special tags, there's no added flexability in one or the other.
In ASP.NET you may use a nice self-contained component - no such concept
exists in WebBroker. Of course, you could write webbroker
components/page-producers to handle tags, but then you'd only be to where
ASP.NET is out of the box.
--
-Jimmy
 

public class Foo{
/// <summary>
/// This method does nothing useful.
/// </summary>
/// <param name="Arg1">This is the first argument</param>
/// <param name="Arg2">This is the second argument</param>
public void IPityDaFoo(string Arg1, string Arg2){
// Do nothing....
}
}
Now when you go to use it in the IDE:
{
Foo MyFoo = new Foo();
MyFoo.|
}
After the | you will see code insight pop-up, select the IPityDaFoo method
and a description will pop up. It will look something like this:
------------
| void IPityDaFoo(string Arg1, string Arg2)
| This method does nothing useful.
------------
Hit the l-paren key and you will get a hint for Arg1, which will look
something like this (bold tags substituted for actual bold text):
------------
| void IPityDaFoo(<b>string Arg1</b>, string Arg2)
| Arg1:
| This is the first argument
------------
It comes in handy quite often, to have documentation immediatly at your
finger tips. I hit the F1 key a lot less than I used to :-).
--
-Jimmy
 

tags>.
So, how's WebBroker give you more control?
--
-Jimmy
 

On Tue, 21 Oct 2003 16:02:18 -0400, "Jimmy [Used-Disks]"
<XXXX@XXXXX.COM>writes:
Nick Hodges - TeamB
Lemanix Corporation
Please always follow the newsgroup guidelines --
www.borland.com/newsgroups
 

On Tue, 21 Oct 2003 16:03:21 -0400, "Jimmy [Used-Disks]"
<XXXX@XXXXX.COM>writes:
HTML output of an <asp:xxx>tag.
Nick Hodges - TeamB
Lemanix Corporation
Please always follow the newsgroup guidelines --
www.borland.com/newsgroups
 

in a <aspx:xx>tag?
--
-Jimmy
 

On Tue, 21 Oct 2003 16:34:53 -0400, "Jimmy [Used-Disks]"
<XXXX@XXXXX.COM>writes:
character/text level what this control does? I can't.
Nick Hodges - TeamB
Lemanix Corporation
Please always follow the newsgroup guidelines --
www.borland.com/newsgroups
 

want to do in ASP.NET what you do in WebBroker, put a tag in the page like
this:
<%#GenerateCalendarHTML()%>
Or this:
<%=GenerateCalendarHTML()%>
(There's an important difference in these lines of code, but both'll do what
you want)
Then in the GenerateCalendarHTML method of your page, spit out any HTML you
want, character by character. You can even add arguments.
I'm still failing to see where WebBroker gives you control and ASP.NET
doesn't...
--
-Jimmy
 

On Tue, 21 Oct 2003 17:36:35 -0400, "Jimmy [Used-Disks]"
<XXXX@XXXXX.COM>writes:
control in ASP.NET and then control the exact output of the HTML that
this control renders.
HTML that the calendar control generates -- a point that can not be
argued, because it is a fact. ;-)
You are shifting the argument each time to the advantage of ASP.NET.
Are we discussing ASP.NET vs. WebBroker? Or ASP.NET vs WebSnap?
You can use ASP.NET just like web broker, and then then they both do
pretty much the same thing -- if you don't use
WebControls/ServerControls, then there is nothing that ASP.NET can't
do that WebBroker/WebSnap can not do equally well.
If you do use Server/WebControls, then you can not provide total control
over the HTML that gets generated.
doesn't provide the control one might want.
Nick Hodges - TeamB
Lemanix Corporation
Please always follow the newsgroup guidelines --
www.borland.com/newsgroups
 

"Nick Hodges (TeamB)" <XXXX@XXXXX.COM>writes
one and it gives you an extreme amount of control over the end result. The
only thing you can not control is that it is rendered as a <table>but it
wouldn't be very difficult to expose that as well.
controls, which are a huge benefit. What about the concept of ViewState? The
global Application object? Session management in server farms? Web User
Controls? DataBinding? 100% Compiled code (even the ASPX Pages are compiled
in ASP.NET).
controls - so I wrote my own. It didn't take any more effort than the
equivalent code would have in WebBroker/WebSnap, plus I was able to expose
all the properties I needed (even on a character-by-character level, when
necessary) for complete control.
controls allow *more* flexibility than WebBroker/WebSnap. How? You can write
your own.
--
-Jimmy
 

On Tue, 21 Oct 2003 20:55:15 -0400, "Jimmy [Used-Disks]"
<XXXX@XXXXX.COM>writes:
But you are missing my point -- ASP.NET has advantages, I agree. But
all I am saying is that there are reasons -- valid reasons -- why you
might not want to use it.
advantages and disadvantages over ASP.NET.
Nick Hodges - TeamB
Lemanix Corporation
Please always follow the newsgroup guidelines --
www.borland.com/newsgroups
 

with Rich Bako's component you can do session handling in server farms, so
I'll give WebSnap that. Also, I don't think WebSnap has Web User Controls...
it has SSI, but that is no where near what a Web User Control does. WebSnap
doesn't have anything like databinding, and the pages in WebSnap are *not*
compiled - they are interpreted.
I also forgot content caching. ASP.NET has that too, WebSnap doesn't.
Other than that, I don't see any good reason to use WebBroker/WebSnap over
ASP.NET (oh wait - legacy code would be good. Any others?). We had a
discussion a while back about WebSnap actions vs. classic events (like
OnClick). I do see benefits there, but have yet come across a practical
real-world example of how this single benefit outweighs all the benefits of
ASP.NET.
Let me make a similar point:
My left foot has advantages and disadvantages over my right foot. :-p
--
-Jimmy