|
 |
asp_components thread: windows script components vs scripting
Message #1 by dont worry <aspmailbox@y...> on Mon, 23 Oct 2000 16:13:59 -0700 (PDT)
|
|
I've read that windows scripting components are not
good for production, but is it better than having
scripting in asp pages?
Thanks
Message #2 by Robert Chartier <rchartierh@a...> on Tue, 24 Oct 2000 08:14:42 -0700
|
|
#1. where have you read "that windows scripting components are not good for
production"....?
#2. scripting is fine in ASP pages
WSC are good for a bit-more OOP approach to solve your problem. I have yet
to see them hold up in a large scale development effort. Currently Iam
involved in one of these large scale efforts based primarily on WSC and a
bit of COM/COM+. So far development is a real pain because of weak
debugging and error output. Be cautious with WSC.
At 04:13 PM 10/23/2000 -0700, you wrote:
>I've read that windows scripting components are not
>good for production, but is it better than having
>scripting in asp pages?
>
>Thanks
>
>
Rob Chartier
rchartierh@a...
Pager: xxx-xxx-xxxx
http://www.aspfree.com/devlinks/
http://www.aspfree.com/authors/robert/
http://www.aspalliance.com/nothingmn/
Message #3 by dont worry <aspmailbox@y...> on Wed, 25 Oct 2000 07:48:09 -0700 (PDT)
|
|
I read that they are only good for prototyping in
Beginning components for asp by wrox. I already have
my code in javascript, should it just port over to
wsc?
Have you load tested with the wsc components you built
yet? How did it go?
Thanks
--- Robert Chartier <rchartierh@a...> wrote:
> #1. where have you read "that windows scripting
> components are not good for
> production"....?
> #2. scripting is fine in ASP pages
>
> WSC are good for a bit-more OOP approach to solve
> your problem. I have yet
> to see them hold up in a large scale development
> effort. Currently Iam
> involved in one of these large scale efforts based
> primarily on WSC and a
> bit of COM/COM+. So far development is a real pain
> because of weak
> debugging and error output. Be cautious with WSC.
>
>
>
> At 04:13 PM 10/23/2000 -0700, you wrote:
> >I've read that windows scripting components are not
> >good for production, but is it better than having
> >scripting in asp pages?
> >
> >Thanks
> >
> >
>
> Rob Chartier
> rchartierh@a...
> Pager: xxx-xxx-xxxx
> http://www.aspfree.com/devlinks/
> http://www.aspfree.com/authors/robert/
> http://www.aspalliance.com/nothingmn/
>
>
Message #4 by Robert Chartier <rchartierh@a...> on Wed, 25 Oct 2000 08:33:09 -0700
|
|
I agree....IMHO i would avoid using WSC for any real large scale
development process. But i was not the point person for this project.
They do provide a good intermediate transition point from straight up ASP
to the COM/COM+ world.
You mentioned that all of your code is in Javascript...considering
Javascript is client only.....maybe your referring to JScript...?
The systems engineer's will be load testing the environment soon. (not
soon enough for me)....I will post whatever results I can.
At 07:48 AM 10/25/2000 -0700, you wrote:
>I read that they are only good for prototyping in
>Beginning components for asp by wrox. I already have
>my code in javascript, should it just port over to
>wsc?
>Have you load tested with the wsc components you built
>yet? How did it go?
>
>Thanks
>--- Robert Chartier <rchartierh@a...> wrote:
> > #1. where have you read "that windows scripting
> > components are not good for
> > production"....?
> > #2. scripting is fine in ASP pages
> >
> > WSC are good for a bit-more OOP approach to solve
> > your problem. I have yet
> > to see them hold up in a large scale development
> > effort. Currently Iam
> > involved in one of these large scale efforts based
> > primarily on WSC and a
> > bit of COM/COM+. So far development is a real pain
> > because of weak
> > debugging and error output. Be cautious with WSC.
> >
> >
> >
> > At 04:13 PM 10/23/2000 -0700, you wrote:
> > >I've read that windows scripting components are not
> > >good for production, but is it better than having
> > >scripting in asp pages?
> > >
> > >Thanks
> > >
> > >
> >
Rob Chartier
rchartierh@a...
Pager: xxx-xxx-xxxx
http://www.aspfree.com/devlinks/
http://www.aspfree.com/authors/robert/
http://www.aspalliance.com/nothingmn/
Message #5 by dont worry <aspmailbox@y...> on Wed, 25 Oct 2000 13:03:27 -0700 (PDT)
|
|
Well, I want to take my asp pages and turn them in to
COM objects for performance benefits and to create a
true n-tier app. My asp pages or in vbscript, I know
that it isn't as easy as copy and pasting into VB to
create the Components althought I wish it was. I 'm
preparing my self for a large task.
(I hate having to shut down Component services
evertime I make a small change...ARGH)
1)What and How should I get this done?
Thanks
--- Robert Chartier <rchartierh@a...> wrote:
> I agree....IMHO i would avoid using WSC for any real
> large scale
> development process. But i was not the point person
> for this project.
>
> They do provide a good intermediate transition point
> from straight up ASP
> to the COM/COM+ world.
>
> You mentioned that all of your code is in
> Javascript...considering
> Javascript is client only.....maybe your referring
> to JScript...?
>
> The systems engineer's will be load testing the
> environment soon. (not
> soon enough for me)....I will post whatever results
> I can.
>
>
>
>
>
>
>
> At 07:48 AM 10/25/2000 -0700, you wrote:
> >I read that they are only good for prototyping in
> >Beginning components for asp by wrox. I already
> have
> >my code in javascript, should it just port over to
> >wsc?
> >Have you load tested with the wsc components you
> built
> >yet? How did it go?
> >
> >Thanks
> >--- Robert Chartier <rchartierh@a...> wrote:
> > > #1. where have you read "that windows scripting
> > > components are not good for
> > > production"....?
> > > #2. scripting is fine in ASP pages
> > >
> > > WSC are good for a bit-more OOP approach to
> solve
> > > your problem. I have yet
> > > to see them hold up in a large scale development
> > > effort. Currently Iam
> > > involved in one of these large scale efforts
> based
> > > primarily on WSC and a
> > > bit of COM/COM+. So far development is a real
> pain
> > > because of weak
> > > debugging and error output. Be cautious with
> WSC.
> > >
> > >
> > >
> > > At 04:13 PM 10/23/2000 -0700, you wrote:
> > > >I've read that windows scripting components are
> not
> > > >good for production, but is it better than
> having
> > > >scripting in asp pages?
> > > >
> > > >Thanks
> > > >
> > > >
> > >
> Rob Chartier
> rchartierh@a...
> Pager: xxx-xxx-xxxx
> http://www.aspfree.com/devlinks/
> http://www.aspfree.com/authors/robert/
> http://www.aspalliance.com/nothingmn/
>
Message #6 by =?Windows-1252?Q?Jenz_R=F6nnow?= <jenz@c...> on Thu, 26 Oct 2000 08:23:00 +0200
|
|
Create an object with Visual Basic. Put into transaction
server or in the COM/COM+ folder on Win2000.
Simply call the object from the ASP page...
BTW; You dont have to shut down the component
service every time you are updating the object.
Just shoose shut down on the package in with
the object are, and then delete the Vlavbla.Class1
and drag the new version into the package ;)
/Jenz, System Developer
-----Original Message-----
From: dont worry [mailto:aspmailbox@y...]
Sent: den 25 oktober 2000 22:03
To: ASP components
Subject: [asp_components] Re: windows script components vs scripting
Well, I want to take my asp pages and turn them in to
COM objects for performance benefits and to create a
true n-tier app. My asp pages or in vbscript, I know
that it isn't as easy as copy and pasting into VB to
create the Components althought I wish it was. I 'm
preparing my self for a large task.
(I hate having to shut down Component services
evertime I make a small change...ARGH)
1)What and How should I get this done?
Thanks
--- Robert Chartier <rchartierh@a...> wrote:
> I agree....IMHO i would avoid using WSC for any real
> large scale
> development process. But i was not the point person
> for this project.
>
> They do provide a good intermediate transition point
> from straight up ASP
> to the COM/COM+ world.
>
> You mentioned that all of your code is in
> Javascript...considering
> Javascript is client only.....maybe your referring
> to JScript...?
>
> The systems engineer's will be load testing the
> environment soon. (not
> soon enough for me)....I will post whatever results
> I can.
>
>
>
>
>
>
>
> At 07:48 AM 10/25/2000 -0700, you wrote:
> >I read that they are only good for prototyping in
> >Beginning components for asp by wrox. I already
> have
> >my code in javascript, should it just port over to
> >wsc?
> >Have you load tested with the wsc components you
> built
> >yet? How did it go?
> >
> >Thanks
> >--- Robert Chartier <rchartierh@a...> wrote:
> > > #1. where have you read "that windows scripting
> > > components are not good for
> > > production"....?
> > > #2. scripting is fine in ASP pages
> > >
> > > WSC are good for a bit-more OOP approach to
> solve
> > > your problem. I have yet
> > > to see them hold up in a large scale development
> > > effort. Currently Iam
> > > involved in one of these large scale efforts
> based
> > > primarily on WSC and a
> > > bit of COM/COM+. So far development is a real
> pain
> > > because of weak
> > > debugging and error output. Be cautious with
> WSC.
> > >
> > >
> > >
> > > At 04:13 PM 10/23/2000 -0700, you wrote:
> > > >I've read that windows scripting components are
> not
> > > >good for production, but is it better than
> having
> > > >scripting in asp pages?
> > > >
> > > >Thanks
> > > >
> > > >
> > >
> Rob Chartier
> rchartierh@a...
> Pager: xxx-xxx-xxxx
> http://www.aspfree.com/devlinks/
> http://www.aspfree.com/authors/robert/
> http://www.aspalliance.com/nothingmn/
>
Message #7 by Robert Chartier <rchartierh@a...> on Wed, 25 Oct 2000 15:06:57 -0700
|
|
the biggest thing you have to consider is if you have a reason to move it
if there is a performance issue, or security, then move it..
for example, you wouldnt want to move some SIMPLE string handling functions
into COM cus it actually could perform worse.
but your COMPLEX handling routines could be moved if the compiled code will
enhance the performance.
security issues could mean that you are wishing to compile the KEY used in
your encryption routine, or other similar things.
so its pretty much your call, if you choose to move it over...just remember
that sometimes its not the best idea.
At 01:03 PM 10/25/2000 -0700, you wrote:
>Well, I want to take my asp pages and turn them in to
>COM objects for performance benefits and to create a
>true n-tier app. My asp pages or in vbscript, I know
>that it isn't as easy as copy and pasting into VB to
>create the Components althought I wish it was. I 'm
>preparing my self for a large task.
>(I hate having to shut down Component services
>evertime I make a small change...ARGH)
>
>1)What and How should I get this done?
>
>Thanks
>--- Robert Chartier <rchartierh@a...> wrote:
> > I agree....IMHO i would avoid using WSC for any real
> > large scale
>
> > development process. But i was not the point person
> > for this project.
> >
> > They do provide a good intermediate transition point
> > from straight up ASP
> > to the COM/COM+ world.
> >
> > You mentioned that all of your code is in
> > Javascript...considering
> > Javascript is client only.....maybe your referring
> > to JScript...?
> >
> > The systems engineer's will be load testing the
> > environment soon. (not
> > soon enough for me)....I will post whatever results
> > I can.
> >
> >
> >
> >
> >
> >
> >
> > At 07:48 AM 10/25/2000 -0700, you wrote:
> > >I read that they are only good for prototyping in
> > >Beginning components for asp by wrox. I already
> > have
> > >my code in javascript, should it just port over to
> > >wsc?
> > >Have you load tested with the wsc components you
> > built
> > >yet? How did it go?
> > >
> > >Thanks
> > >--- Robert Chartier <rchartierh@a...> wrote:
> > > > #1. where have you read "that windows scripting
> > > > components are not good for
> > > > production"....?
> > > > #2. scripting is fine in ASP pages
> > > >
> > > > WSC are good for a bit-more OOP approach to
> > solve
> > > > your problem. I have yet
> > > > to see them hold up in a large scale development
> > > > effort. Currently Iam
> > > > involved in one of these large scale efforts
> > based
> > > > primarily on WSC and a
> > > > bit of COM/COM+. So far development is a real
> > pain
> > > > because of weak
> > > > debugging and error output. Be cautious with
> > WSC.
> > > >
> > > >
> > > >
> > > > At 04:13 PM 10/23/2000 -0700, you wrote:
> > > > >I've read that windows scripting components are
> > not
> > > > >good for production, but is it better than
> > having
> > > > >scripting in asp pages?
> > > > >
> > > > >Thanks
> > > > >
> > > > >
> > > >
> > Rob Chartier
> > rchartierh@a...
> > Pager: xxx-xxx-xxxx
> > http://www.aspfree.com/devlinks/
> > http://www.aspfree.com/authors/robert/
> > http://www.aspalliance.com/nothingmn/
> >
>
Rob Chartier
rchartierh@a...
Pager: xxx-xxx-xxxx
http://www.aspfree.com/devlinks/
http://www.aspfree.com/authors/robert/
http://www.aspalliance.com/nothingmn/
|
|
|
View Cart
