Hi,
i have written a web app using ATL server, it has file upload that is
working great on the test machine which is vista with IIS7, but it doesnt
uplad files larger than about 65MB on the production or any windows 2003
server with IIS6, note that i have asp.net applications running on that 2k3 
server that are uploading larger files no problems.
what happens is the w3wp.exe remains the same size in memory and the server
closes the connection instantly and the client detects that after 5 minutes,
but when the file is less than 65MB the w3wp.exe increases in memory size as
much as the uploaded file size and the file is uploaded.
i have ovewritten the 2 form upload related functions as follows in the
handler .h:
inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is equals to
1GB.
the web app is configured to have its own app pool that has all default 
settings.

any ideas why? i have found people with same problem but i couldnt find a 
solution for it anywhere on
the net, and am not sure if its caused by IIS or ATL.

Thanks

On Apr 15, 7:03 am, "Imad"  wrote:
> Hi,
> i have written a web app using ATL server, it has file upload that is
> working great on the test machine which is vista with IIS7, but it doesnt
> uplad files larger than about 65MB on the production or any windows 2003
> server with IIS6, note that i have asp.net applications running on that 2k3
> server that are uploading larger files no problems.
> what happens is the w3wp.exe remains the same size in memory and the server
> closes the connection instantly and the client detects that after 5 minutes,
> but when the file is less than 65MB the w3wp.exe increases in memory size as
> much as the uploaded file size and the file is uploaded.
> i have ovewritten the 2 form upload related functions as follows in the
> handler .h:
> inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is equals to
> 1GB.
> the web app is configured to have its own app pool that has all default
> settings.
>
> any ideas why? i have found people with same problem but i couldnt find a
> solution for it anywhere on
> the net, and am not sure if its caused by IIS or ATL.
>
> Thanks


It has to be ATL limitation.

ASP.Net is an ISAPI Extension on wrapper on managed code IIS which you
say has no such limitation.
ATL Server is another ISAPI Extension wrapper on IIS which you say has
such limitation.
I have my pure ISAPI Extension to accept POSTed uploads which has no
such limitation.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

but if it was atl limitation it would also be limited under IIS7?
what kind of solution do you choose in VS2005 for pure ISAPI extension?

Imad


"David Wang"  wrote in message 
news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com...
On Apr 15, 7:03 am, "Imad"  wrote:
> Hi,
> i have written a web app using ATL server, it has file upload that is
> working great on the test machine which is vista with IIS7, but it doesnt
> uplad files larger than about 65MB on the production or any windows 2003
> server with IIS6, note that i have asp.net applications running on that 
> 2k3
> server that are uploading larger files no problems.
> what happens is the w3wp.exe remains the same size in memory and the 
> server
> closes the connection instantly and the client detects that after 5 
> minutes,
> but when the file is less than 65MB the w3wp.exe increases in memory size 
> as
> much as the uploaded file size and the file is uploaded.
> i have ovewritten the 2 form upload related functions as follows in the
> handler .h:
> inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is equals to
> 1GB.
> the web app is configured to have its own app pool that has all default
> settings.
>
> any ideas why? i have found people with same problem but i couldnt find a
> solution for it anywhere on
> the net, and am not sure if its caused by IIS or ATL.
>
> Thanks


It has to be ATL limitation.

ASP.Net is an ISAPI Extension on wrapper on managed code IIS which you
say has no such limitation.
ATL Server is another ISAPI Extension wrapper on IIS which you say has
such limitation.
I have my pure ISAPI Extension to accept POSTed uploads which has no
such limitation.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Just build a plain Win32 DLL which exports GetExtensionVersion and
HttpExtensionProc. No special solution necessary.

http://blogs.msdn.com/david.wang/archive/2006/03/25/MFC-ISAPI-Template-and-ISAPI-Development.aspx

http://blogs.msdn.com/david.wang/archive/2005/12/19/HOWTO-Compile-and-Use-my-ISAPI-Code-Samples.aspx


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Apr 16, 6:08 am, "Imad"  wrote:
> but if it was atl limitation it would also be limited under IIS7?
> what kind of solution do you choose in VS2005 for pure ISAPI extension?
>
> Imad
>
> "David Wang"  wrote in message
>
> news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com...
> On Apr 15, 7:03 am, "Imad"  wrote:
>
>
>
>
>
> > Hi,
> > i have written a web app using ATL server, it has file upload that is
> > working great on the test machine which is vista with IIS7, but it doesnt
> > uplad files larger than about 65MB on the production or any windows 2003> > server with IIS6, note that i have asp.net applications running on that
> > 2k3
> > server that are uploading larger files no problems.
> > what happens is the w3wp.exe remains the same size in memory and the
> > server
> > closes the connection instantly and the client detects that after 5
> > minutes,
> > but when the file is less than 65MB the w3wp.exe increases in memory size
> > as
> > much as the uploaded file size and the file is uploaded.
> > i have ovewritten the 2 form upload related functions as follows in the
> > handler .h:
> > inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> > inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> > and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is equals to
> > 1GB.
> > the web app is configured to have its own app pool that has all default
> > settings.
>
> > any ideas why? i have found people with same problem but i couldnt find a
> > solution for it anywhere on
> > the net, and am not sure if its caused by IIS or ATL.
>
> > Thanks
>
> It has to be ATL limitation.
>
> ASP.Net is an ISAPI Extension on wrapper on managed code IIS which you
> say has no such limitation.
> ATL Server is another ISAPI Extension wrapper on IIS which you say has
> such limitation.
> I have my pure ISAPI Extension to accept POSTed uploads which has no
> such limitation.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //- Hide quoted text -
>
> - Show quoted text -

sorry, posted to sender instead of to group by mistake and was wondering why 
it was taking long to appear, will repost to group.

are you absolutely sure that the atl server wont allow uploads for files
larger than 65MB?
because we have a big problem, when we started building the site and
recommended this platform there was no limitation of such kind mentioned
anywhere on microsoft msdn or in the documentations, now we have an angry
customer that cannot wait for us to rebuild his site (that took us 6 months
and 4 developers to build with atl so you can imagine our loss if we were to
rebuild) and not being able to upload large files is not acceptable for him.
please i need a solution for this, if you cannot give me answers please
direct me if you can.

Thanks

Imad

"David Wang"  wrote in message 
news:6815dee0-259e-4817-92e0-8e364e99b1c2@m73g2000hsh.googlegroups.com...
Just build a plain Win32 DLL which exports GetExtensionVersion and
HttpExtensionProc. No special solution necessary.

http://blogs.msdn.com/david.wang/archive/2006/03/25/MFC-ISAPI-Template-and-ISAPI-Development.aspx

http://blogs.msdn.com/david.wang/archive/2005/12/19/HOWTO-Compile-and-Use-my-ISAPI-Code-Samples.aspx


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Apr 16, 6:08 am, "Imad"  wrote:
> but if it was atl limitation it would also be limited under IIS7?
> what kind of solution do you choose in VS2005 for pure ISAPI extension?
>
> Imad
>
> "David Wang"  wrote in message
>
> news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com...
> On Apr 15, 7:03 am, "Imad"  wrote:
>
>
>
>
>
> > Hi,
> > i have written a web app using ATL server, it has file upload that is
> > working great on the test machine which is vista with IIS7, but it 
> > doesnt
> > uplad files larger than about 65MB on the production or any windows 2003
> > server with IIS6, note that i have asp.net applications running on that
> > 2k3
> > server that are uploading larger files no problems.
> > what happens is the w3wp.exe remains the same size in memory and the
> > server
> > closes the connection instantly and the client detects that after 5
> > minutes,
> > but when the file is less than 65MB the w3wp.exe increases in memory 
> > size
> > as
> > much as the uploaded file size and the file is uploaded.
> > i have ovewritten the 2 form upload related functions as follows in the
> > handler .h:
> > inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> > inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> > and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is equals 
> > to
> > 1GB.
> > the web app is configured to have its own app pool that has all default
> > settings.
>
> > any ideas why? i have found people with same problem but i couldnt find 
> > a
> > solution for it anywhere on
> > the net, and am not sure if its caused by IIS or ATL.
>
> > Thanks
>
> It has to be ATL limitation.
>
> ASP.Net is an ISAPI Extension on wrapper on managed code IIS which you
> say has no such limitation.
> ATL Server is another ISAPI Extension wrapper on IIS which you say has
> such limitation.
> I have my pure ISAPI Extension to accept POSTed uploads which has no
> such limitation.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //- Hide quoted text -
>
> - Show quoted text -

I understand the pressure you are under. Most people posting questions
tend to be under some sort of pressure.

I don't know ATL Server well enough to configure it. I always write
pure ISAPI code and never use things like ATL Server.

I can only tell you that ISAPI and IIS itself does not have such
upload size limit. If you are encountering limits, it is either in ATL
Server (the layer on top of ISAPI that you are using) or something in
the network connectivity layer underneath IIS. Usually people remember
configuring such limits in the network layer, so I say it's in ATL.

No matter what, the client must also verify that their production
environment, including the production server and its network, load
balancer, proxy servers, etc are not throttling requests anywhere,
even inadvertently, and can support posts >64MB.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//



On Apr 18, 8:23 am, "Imad"  wrote:
> sorry, posted to sender instead of to group by mistake and was wondering why
> it was taking long to appear, will repost to group.
>
> are you absolutely sure that the atl server wont allow uploads for files
> larger than 65MB?
> because we have a big problem, when we started building the site and
> recommended this platform there was no limitation of such kind mentioned
> anywhere on microsoft msdn or in the documentations, now we have an angry
> customer that cannot wait for us to rebuild his site (that took us 6 months
> and 4 developers to build with atl so you can imagine our loss if we were to
> rebuild) and not being able to upload large files is not acceptable for him.
> please i need a solution for this, if you cannot give me answers please
> direct me if you can.
>
> Thanks
>
> Imad
>
> "David Wang"  wrote in message
>
> news:6815dee0-259e-4817-92e0-8e364e99b1c2@m73g2000hsh.googlegroups.com...
> Just build a plain Win32 DLL which exports GetExtensionVersion and
> HttpExtensionProc. No special solution necessary.
>
> http://blogs.msdn.com/david.wang/archive/2006/03/25/MFC-ISAPI-Templat...
>
> http://blogs.msdn.com/david.wang/archive/2005/12/19/HOWTO-Compile-and...
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Apr 16, 6:08 am, "Imad"  wrote:
>
>
>
> > but if it was atl limitation it would also be limited under IIS7?
> > what kind of solution do you choose in VS2005 for pure ISAPI extension?
>
> > Imad
>
> > "David Wang"  wrote in message
>
> >news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com...
> > On Apr 15, 7:03 am, "Imad"  wrote:
>
> > > Hi,
> > > i have written a web app using ATL server, it has file upload that is
> > > working great on the test machine which is vista with IIS7, but it
> > > doesnt
> > > uplad files larger than about 65MB on the production or any windows 2003
> > > server with IIS6, note that i have asp.net applications running on that
> > > 2k3
> > > server that are uploading larger files no problems.
> > > what happens is the w3wp.exe remains the same size in memory and the
> > > server
> > > closes the connection instantly and the client detects that after 5
> > > minutes,
> > > but when the file is less than 65MB the w3wp.exe increases in memory
> > > size
> > > as
> > > much as the uploaded file size and the file is uploaded.
> > > i have ovewritten the 2 form upload related functions as follows in the
> > > handler .h:
> > > inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> > > inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> > > and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is equals> > > to
> > > 1GB.
> > > the web app is configured to have its own app pool that has all default
> > > settings.
>
> > > any ideas why? i have found people with same problem but i couldnt find
> > > a
> > > solution for it anywhere on
> > > the net, and am not sure if its caused by IIS or ATL.
>
> > > Thanks
>
> > It has to be ATL limitation.
>
> > ASP.Net is an ISAPI Extension on wrapper on managed code IIS which you
> > say has no such limitation.
> > ATL Server is another ISAPI Extension wrapper on IIS which you say has
> > such limitation.
> > I have my pure ISAPI Extension to accept POSTed uploads which has no
> > such limitation.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Thank you for your reply,
i have created a pure ISAPI upload and it worked for over 65MB uploads on 
IIS6 on the same server,
so thats confirmed that its an ATL problem under IIS6 because the same app 
works fine under IIS7,
i have already posted my problem in the atl newsgroup because i wasnt sure 
weather it was an iis or atl problem but havent got a reply, do you know 
where i can post to find answers as to if there is a solution around it to 
make atl server based ISAPI upload larger than 65MB under IIS6?

Thanks

Imad


"David Wang"  wrote in message 
news:b6830a63-59bf-4334-80ba-4ae3ed889b32@w5g2000prd.googlegroups.com...
I understand the pressure you are under. Most people posting questions
tend to be under some sort of pressure.

I don't know ATL Server well enough to configure it. I always write
pure ISAPI code and never use things like ATL Server.

I can only tell you that ISAPI and IIS itself does not have such
upload size limit. If you are encountering limits, it is either in ATL
Server (the layer on top of ISAPI that you are using) or something in
the network connectivity layer underneath IIS. Usually people remember
configuring such limits in the network layer, so I say it's in ATL.

No matter what, the client must also verify that their production
environment, including the production server and its network, load
balancer, proxy servers, etc are not throttling requests anywhere,
even inadvertently, and can support posts >64MB.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//



On Apr 18, 8:23 am, "Imad"  wrote:
> sorry, posted to sender instead of to group by mistake and was wondering 
> why
> it was taking long to appear, will repost to group.
>
> are you absolutely sure that the atl server wont allow uploads for files
> larger than 65MB?
> because we have a big problem, when we started building the site and
> recommended this platform there was no limitation of such kind mentioned
> anywhere on microsoft msdn or in the documentations, now we have an angry
> customer that cannot wait for us to rebuild his site (that took us 6 
> months
> and 4 developers to build with atl so you can imagine our loss if we were 
> to
> rebuild) and not being able to upload large files is not acceptable for 
> him.
> please i need a solution for this, if you cannot give me answers please
> direct me if you can.
>
> Thanks
>
> Imad
>
> "David Wang"  wrote in message
>
> news:6815dee0-259e-4817-92e0-8e364e99b1c2@m73g2000hsh.googlegroups.com...
> Just build a plain Win32 DLL which exports GetExtensionVersion and
> HttpExtensionProc. No special solution necessary.
>
> http://blogs.msdn.com/david.wang/archive/2006/03/25/MFC-ISAPI-Templat...
>
> http://blogs.msdn.com/david.wang/archive/2005/12/19/HOWTO-Compile-and...
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Apr 16, 6:08 am, "Imad"  wrote:
>
>
>
> > but if it was atl limitation it would also be limited under IIS7?
> > what kind of solution do you choose in VS2005 for pure ISAPI extension?
>
> > Imad
>
> > "David Wang"  wrote in message
>
> >news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com...
> > On Apr 15, 7:03 am, "Imad"  wrote:
>
> > > Hi,
> > > i have written a web app using ATL server, it has file upload that is
> > > working great on the test machine which is vista with IIS7, but it
> > > doesnt
> > > uplad files larger than about 65MB on the production or any windows 
> > > 2003
> > > server with IIS6, note that i have asp.net applications running on 
> > > that
> > > 2k3
> > > server that are uploading larger files no problems.
> > > what happens is the w3wp.exe remains the same size in memory and the
> > > server
> > > closes the connection instantly and the client detects that after 5
> > > minutes,
> > > but when the file is less than 65MB the w3wp.exe increases in memory
> > > size
> > > as
> > > much as the uploaded file size and the file is uploaded.
> > > i have ovewritten the 2 form upload related functions as follows in 
> > > the
> > > handler .h:
> > > inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> > > inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> > > and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is equals
> > > to
> > > 1GB.
> > > the web app is configured to have its own app pool that has all 
> > > default
> > > settings.
>
> > > any ideas why? i have found people with same problem but i couldnt 
> > > find
> > > a
> > > solution for it anywhere on
> > > the net, and am not sure if its caused by IIS or ATL.
>
> > > Thanks
>
> > It has to be ATL limitation.
>
> > ASP.Net is an ISAPI Extension on wrapper on managed code IIS which you
> > say has no such limitation.
> > ATL Server is another ISAPI Extension wrapper on IIS which you say has
> > such limitation.
> > I have my pure ISAPI Extension to accept POSTed uploads which has no
> > such limitation.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Sorry, I really do not use ATL nor know where it is supported.

Personally, I don't see a need to use ATL if you are just writing
plain ISAPI. And the proper way to support large uploads is NOT to
buffer the entire thing to memory (which is what you observe) but to
stream, and you'll need to code that.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//



On Apr 25, 9:43 am, "Imad"  wrote:
> Thank you for your reply,
> i have created a pure ISAPI upload and it worked for over 65MB uploads on
> IIS6 on the same server,
> so thats confirmed that its an ATL problem under IIS6 because the same app> works fine under IIS7,
> i have already posted my problem in the atl newsgroup because i wasnt sure> weather it was an iis or atl problem but havent got a reply, do you know
> where i can post to find answers as to if there is a solution around it to> make atl server based ISAPI upload larger than 65MB under IIS6?
>
> Thanks
>
> Imad
>
> "David Wang"  wrote in message
>
> news:b6830a63-59bf-4334-80ba-4ae3ed889b32@w5g2000prd.googlegroups.com...
> I understand the pressure you are under. Most people posting questions
> tend to be under some sort of pressure.
>
> I don't know ATL Server well enough to configure it. I always write
> pure ISAPI code and never use things like ATL Server.
>
> I can only tell you that ISAPI and IIS itself does not have such
> upload size limit. If you are encountering limits, it is either in ATL
> Server (the layer on top of ISAPI that you are using) or something in
> the network connectivity layer underneath IIS. Usually people remember
> configuring such limits in the network layer, so I say it's in ATL.
>
> No matter what, the client must also verify that their production
> environment, including the production server and its network, load
> balancer, proxy servers, etc are not throttling requests anywhere,
> even inadvertently, and can support posts >64MB.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Apr 18, 8:23 am, "Imad"  wrote:
>
>
>
> > sorry, posted to sender instead of to group by mistake and was wondering> > why
> > it was taking long to appear, will repost to group.
>
> > are you absolutely sure that the atl server wont allow uploads for files> > larger than 65MB?
> > because we have a big problem, when we started building the site and
> > recommended this platform there was no limitation of such kind mentioned> > anywhere on microsoft msdn or in the documentations, now we have an angry
> > customer that cannot wait for us to rebuild his site (that took us 6
> > months
> > and 4 developers to build with atl so you can imagine our loss if we were
> > to
> > rebuild) and not being able to upload large files is not acceptable for
> > him.
> > please i need a solution for this, if you cannot give me answers please
> > direct me if you can.
>
> > Thanks
>
> > Imad
>
> > "David Wang"  wrote in message
>
> >news:6815dee0-259e-4817-92e0-8e364e99b1c2@m73g2000hsh.googlegroups.com...> > Just build a plain Win32 DLL which exports GetExtensionVersion and
> > HttpExtensionProc. No special solution necessary.
>
> >http://blogs.msdn.com/david.wang/archive/2006/03/25/MFC-ISAPI-Templat...
>
> >http://blogs.msdn.com/david.wang/archive/2005/12/19/HOWTO-Compile-and...
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //
>
> > On Apr 16, 6:08 am, "Imad"  wrote:
>
> > > but if it was atl limitation it would also be limited under IIS7?
> > > what kind of solution do you choose in VS2005 for pure ISAPI extension> > > Imad
>
> > > "David Wang"  wrote in message
>
> > >news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com..> > > On Apr 15, 7:03 am, "Imad"  wrote:
>
> > > > Hi,
> > > > i have written a web app using ATL server, it has file upload that is
> > > > working great on the test machine which is vista with IIS7, but it
> > > > doesnt
> > > > uplad files larger than about 65MB on the production or any windows
> > > > 2003
> > > > server with IIS6, note that i have asp.net applications running on
> > > > that
> > > > 2k3
> > > > server that are uploading larger files no problems.
> > > > what happens is the w3wp.exe remains the same size in memory and the> > > > server
> > > > closes the connection instantly and the client detects that after 5
> > > > minutes,
> > > > but when the file is less than 65MB the w3wp.exe increases in memory> > > > size
> > > > as
> > > > much as the uploaded file size and the file is uploaded.
> > > > i have ovewritten the 2 form upload related functions as follows in
> > > > the
> > > > handler .h:
> > > > inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> > > > inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> > > > and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is equals
> > > > to
> > > > 1GB.
> > > > the web app is configured to have its own app pool that has all
> > > > default
> > > > settings.
>
> > > > any ideas why? i have found people with same problem but i couldnt
> > > > find
> > > > a
> > > > solution for it anywhere on
> > > > the net, and am not sure if its caused by IIS or ATL.
>
> > > > Thanks
>
> > > It has to be ATL limitation.
>
> > > ASP.Net is an ISAPI Extension on wrapper on managed code IIS which you> > > say has no such limitation.
> > > ATL Server is another ISAPI Extension wrapper on IIS which you say has> > > such limitation.
> > > I have my pure ISAPI Extension to accept POSTed uploads which has no
> > > such limitation.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > //- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

large file upload is just a small but important role of that website.
why we chose atl is speed of development and the fact that any web designer 
can change the layout of the site with html code only.
atl already implements session, cookies and oledb connections to say the 
least so we would have had to reinvent the wheel if working with pure ISAPI 
but of course we didnt know about the limitation of file uploads at the time 
as it wasnt mentionned anywhere.
do you have a link for a sample of pure ISAPI upload to stream rather than 
buffering to memory, as our fastest solution now would be to keep what we 
done and just handle the upload in a seperate module.

Thanks

Imad


"David Wang"  wrote in message 
news:a7d1bce2-cfbb-4f82-9cdd-88b5f8829acd@p39g2000prm.googlegroups.com...
Sorry, I really do not use ATL nor know where it is supported.

Personally, I don't see a need to use ATL if you are just writing
plain ISAPI. And the proper way to support large uploads is NOT to
buffer the entire thing to memory (which is what you observe) but to
stream, and you'll need to code that.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//



On Apr 25, 9:43 am, "Imad"  wrote:
> Thank you for your reply,
> i have created a pure ISAPI upload and it worked for over 65MB uploads on
> IIS6 on the same server,
> so thats confirmed that its an ATL problem under IIS6 because the same app
> works fine under IIS7,
> i have already posted my problem in the atl newsgroup because i wasnt sure
> weather it was an iis or atl problem but havent got a reply, do you know
> where i can post to find answers as to if there is a solution around it to
> make atl server based ISAPI upload larger than 65MB under IIS6?
>
> Thanks
>
> Imad
>
> "David Wang"  wrote in message
>
> news:b6830a63-59bf-4334-80ba-4ae3ed889b32@w5g2000prd.googlegroups.com...
> I understand the pressure you are under. Most people posting questions
> tend to be under some sort of pressure.
>
> I don't know ATL Server well enough to configure it. I always write
> pure ISAPI code and never use things like ATL Server.
>
> I can only tell you that ISAPI and IIS itself does not have such
> upload size limit. If you are encountering limits, it is either in ATL
> Server (the layer on top of ISAPI that you are using) or something in
> the network connectivity layer underneath IIS. Usually people remember
> configuring such limits in the network layer, so I say it's in ATL.
>
> No matter what, the client must also verify that their production
> environment, including the production server and its network, load
> balancer, proxy servers, etc are not throttling requests anywhere,
> even inadvertently, and can support posts >64MB.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Apr 18, 8:23 am, "Imad"  wrote:
>
>
>
> > sorry, posted to sender instead of to group by mistake and was wondering
> > why
> > it was taking long to appear, will repost to group.
>
> > are you absolutely sure that the atl server wont allow uploads for files
> > larger than 65MB?
> > because we have a big problem, when we started building the site and
> > recommended this platform there was no limitation of such kind mentioned
> > anywhere on microsoft msdn or in the documentations, now we have an 
> > angry
> > customer that cannot wait for us to rebuild his site (that took us 6
> > months
> > and 4 developers to build with atl so you can imagine our loss if we 
> > were
> > to
> > rebuild) and not being able to upload large files is not acceptable for
> > him.
> > please i need a solution for this, if you cannot give me answers please
> > direct me if you can.
>
> > Thanks
>
> > Imad
>
> > "David Wang"  wrote in message
>
> >news:6815dee0-259e-4817-92e0-8e364e99b1c2@m73g2000hsh.googlegroups.com...
> > Just build a plain Win32 DLL which exports GetExtensionVersion and
> > HttpExtensionProc. No special solution necessary.
>
> >http://blogs.msdn.com/david.wang/archive/2006/03/25/MFC-ISAPI-Templat...
>
> >http://blogs.msdn.com/david.wang/archive/2005/12/19/HOWTO-Compile-and...
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //
>
> > On Apr 16, 6:08 am, "Imad"  wrote:
>
> > > but if it was atl limitation it would also be limited under IIS7?
> > > what kind of solution do you choose in VS2005 for pure ISAPI 
> > > extension?
>
> > > Imad
>
> > > "David Wang"  wrote in message
>
> > >news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com...
> > > On Apr 15, 7:03 am, "Imad"  wrote:
>
> > > > Hi,
> > > > i have written a web app using ATL server, it has file upload that 
> > > > is
> > > > working great on the test machine which is vista with IIS7, but it
> > > > doesnt
> > > > uplad files larger than about 65MB on the production or any windows
> > > > 2003
> > > > server with IIS6, note that i have asp.net applications running on
> > > > that
> > > > 2k3
> > > > server that are uploading larger files no problems.
> > > > what happens is the w3wp.exe remains the same size in memory and the
> > > > server
> > > > closes the connection instantly and the client detects that after 5
> > > > minutes,
> > > > but when the file is less than 65MB the w3wp.exe increases in memory
> > > > size
> > > > as
> > > > much as the uploaded file size and the file is uploaded.
> > > > i have ovewritten the 2 form upload related functions as follows in
> > > > the
> > > > handler .h:
> > > > inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> > > > inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> > > > and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is 
> > > > equals
> > > > to
> > > > 1GB.
> > > > the web app is configured to have its own app pool that has all
> > > > default
> > > > settings.
>
> > > > any ideas why? i have found people with same problem but i couldnt
> > > > find
> > > > a
> > > > solution for it anywhere on
> > > > the net, and am not sure if its caused by IIS or ATL.
>
> > > > Thanks
>
> > > It has to be ATL limitation.
>
> > > ASP.Net is an ISAPI Extension on wrapper on managed code IIS which you
> > > say has no such limitation.
> > > ATL Server is another ISAPI Extension wrapper on IIS which you say has
> > > such limitation.
> > > I have my pure ISAPI Extension to accept POSTed uploads which has no
> > > such limitation.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > //- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

I find it interesting that you say ATL gives speed of development
because when I think "speed of development", I think of ASP.Net and
Visual Web Developer or even ASP/PHP. ATL/MFC predates those
technologies and in comparison to those later technologies, it only
provides the bare basics. One main difference is that ATL is in native
code instead of managed or interpreted code like ASP.Net or ASP.
Hence, I find it interesting that you say native code gives you speed
of development because most people would say otherwise. Unless you
only have ATL experts and not ASP/ASP.Net experts on hand. ASP.Net
Master Pages exceeds everything you said were advantages in ATL, and
then some.

Sorry, I don't have that sample code at hand, but I know it can be
done. with asynchronous IO to not tie up any threads. You should not
have trouble with this task if ATL gives you speed of development.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Apr 27, 10:05 am, "Imad"  wrote:
> large file upload is just a small but important role of that website.
> why we chose atl is speed of development and the fact that any web designer
> can change the layout of the site with html code only.
> atl already implements session, cookies and oledb connections to say the
> least so we would have had to reinvent the wheel if working with pure ISAPI
> but of course we didnt know about the limitation of file uploads at the time
> as it wasnt mentionned anywhere.
> do you have a link for a sample of pure ISAPI upload to stream rather than> buffering to memory, as our fastest solution now would be to keep what we
> done and just handle the upload in a seperate module.
>
> Thanks
>
> Imad
>
> "David Wang"  wrote in message
>
> news:a7d1bce2-cfbb-4f82-9cdd-88b5f8829acd@p39g2000prm.googlegroups.com...
> Sorry, I really do not use ATL nor know where it is supported.
>
> Personally, I don't see a need to use ATL if you are just writing
> plain ISAPI. And the proper way to support large uploads is NOT to
> buffer the entire thing to memory (which is what you observe) but to
> stream, and you'll need to code that.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Apr 25, 9:43 am, "Imad"  wrote:
>
>
>
> > Thank you for your reply,
> > i have created a pure ISAPI upload and it worked for over 65MB uploads on
> > IIS6 on the same server,
> > so thats confirmed that its an ATL problem under IIS6 because the same app
> > works fine under IIS7,
> > i have already posted my problem in the atl newsgroup because i wasnt sure
> > weather it was an iis or atl problem but havent got a reply, do you know> > where i can post to find answers as to if there is a solution around it to
> > make atl server based ISAPI upload larger than 65MB under IIS6?
>
> > Thanks
>
> > Imad
>
> > "David Wang"  wrote in message
>
> >news:b6830a63-59bf-4334-80ba-4ae3ed889b32@w5g2000prd.googlegroups.com...
> > I understand the pressure you are under. Most people posting questions
> > tend to be under some sort of pressure.
>
> > I don't know ATL Server well enough to configure it. I always write
> > pure ISAPI code and never use things like ATL Server.
>
> > I can only tell you that ISAPI and IIS itself does not have such
> > upload size limit. If you are encountering limits, it is either in ATL
> > Server (the layer on top of ISAPI that you are using) or something in
> > the network connectivity layer underneath IIS. Usually people remember
> > configuring such limits in the network layer, so I say it's in ATL.
>
> > No matter what, the client must also verify that their production
> > environment, including the production server and its network, load
> > balancer, proxy servers, etc are not throttling requests anywhere,
> > even inadvertently, and can support posts >64MB.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //
>
> > On Apr 18, 8:23 am, "Imad"  wrote:
>
> > > sorry, posted to sender instead of to group by mistake and was wondering
> > > why
> > > it was taking long to appear, will repost to group.
>
> > > are you absolutely sure that the atl server wont allow uploads for files
> > > larger than 65MB?
> > > because we have a big problem, when we started building the site and
> > > recommended this platform there was no limitation of such kind mentioned
> > > anywhere on microsoft msdn or in the documentations, now we have an
> > > angry
> > > customer that cannot wait for us to rebuild his site (that took us 6
> > > months
> > > and 4 developers to build with atl so you can imagine our loss if we
> > > were
> > > to
> > > rebuild) and not being able to upload large files is not acceptable for
> > > him.
> > > please i need a solution for this, if you cannot give me answers please
> > > direct me if you can.
>
> > > Thanks
>
> > > Imad
>
> > > "David Wang"  wrote in message
>
> > >news:6815dee0-259e-4817-92e0-8e364e99b1c2@m73g2000hsh.googlegroups.com.> > > Just build a plain Win32 DLL which exports GetExtensionVersion and
> > > HttpExtensionProc. No special solution necessary.
>
> > >http://blogs.msdn.com/david.wang/archive/2006/03/25/MFC-ISAPI-Templat..> > >http://blogs.msdn.com/david.wang/archive/2005/12/19/HOWTO-Compile-and..> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > //
>
> > > On Apr 16, 6:08 am, "Imad"  wrote:
>
> > > > but if it was atl limitation it would also be limited under IIS7?
> > > > what kind of solution do you choose in VS2005 for pure ISAPI
> > > > extension?
>
> > > > Imad
>
> > > > "David Wang"  wrote in message
>
> > > >news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com> > > > On Apr 15, 7:03 am, "Imad"  wrote:
>
> > > > > Hi,
> > > > > i have written a web app using ATL server, it has file upload that> > > > > is
> > > > > working great on the test machine which is vista with IIS7, but it> > > > > doesnt
> > > > > uplad files larger than about 65MB on the production or any windows
> > > > > 2003
> > > > > server with IIS6, note that i have asp.net applications running on> > > > > that
> > > > > 2k3
> > > > > server that are uploading larger files no problems.
> > > > > what happens is the w3wp.exe remains the same size in memory and the
> > > > > server
> > > > > closes the connection instantly and the client detects that after 5
> > > > > minutes,
> > > > > but when the file is less than 65MB the w3wp.exe increases in memory
> > > > > size
> > > > > as
> > > > > much as the uploaded file size and the file is uploaded.
> > > > > i have ovewritten the 2 form upload related functions as follows in
> > > > > the
> > > > > handler .h:
> > > > > inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> > > > > inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> > > > > and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is
> > > > > equals
> > > > > to
> > > > > 1GB.
> > > > > the web app is configured to have its own app pool that has all
> > > > > default
> > > > > settings.
>
> > > > > any ideas why? i have found people with same problem but i couldnt> > > > > find
> > > > > a
> > > > > solution for it anywhere on
> > > > > the net, and am not sure if its caused by IIS or ATL.
>
> > > > > Thanks
>
> > > > It has to be ATL limitation.
>
> > > > ASP.Net is an ISAPI Extension on wrapper on managed code IIS which you
> > > > say has no such limitation.
> > > > ATL Server is another ISAPI Extension wrapper on IIS which you say has
> > > > such limitation.
> > > > I have my pure ISAPI Extension to accept POSTed uploads which has no> > > > such limitation.
>
> > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > > //- Hide quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

am actually surprised of you thinking this way, are we talking about the 
same thing? in vs2005 you choose atl server project. still when it comes to 
speed of development i'de say asp.net is quicker, but we needed a platform 
where whenever a html change was wanted (which is on daily basis) the client 
would be able to do because they have a full time html designer who only 
knows to copy and paste something like {{getsomdatafromisapiatlfunction}} to 
position the data wherever he wants on the page, with asp.net they would 
have had to come back to us to change.
most of our work is done using asp.net because its very stable, it does 
exactly what its asked to do, and its the quickest to get a web app up and 
running but unfortunatly for that solution it wasnt, i know we could do 
things to get around that like creating html templates where the client can 
edit but didnt see the need since it already existed in atl and we all have 
experience in c++ so we had no problems doing things quick enough with atl 
server type of solution.

Thanks

Imad


"David Wang"  wrote in message 
news:628497a8-48ad-4ee5-88b8-63088a8c9598@i36g2000prf.googlegroups.com...
I find it interesting that you say ATL gives speed of development
because when I think "speed of development", I think of ASP.Net and
Visual Web Developer or even ASP/PHP. ATL/MFC predates those
technologies and in comparison to those later technologies, it only
provides the bare basics. One main difference is that ATL is in native
code instead of managed or interpreted code like ASP.Net or ASP.
Hence, I find it interesting that you say native code gives you speed
of development because most people would say otherwise. Unless you
only have ATL experts and not ASP/ASP.Net experts on hand. ASP.Net
Master Pages exceeds everything you said were advantages in ATL, and
then some.

Sorry, I don't have that sample code at hand, but I know it can be
done. with asynchronous IO to not tie up any threads. You should not
have trouble with this task if ATL gives you speed of development.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Apr 27, 10:05 am, "Imad"  wrote:
> large file upload is just a small but important role of that website.
> why we chose atl is speed of development and the fact that any web 
> designer
> can change the layout of the site with html code only.
> atl already implements session, cookies and oledb connections to say the
> least so we would have had to reinvent the wheel if working with pure 
> ISAPI
> but of course we didnt know about the limitation of file uploads at the 
> time
> as it wasnt mentionned anywhere.
> do you have a link for a sample of pure ISAPI upload to stream rather than
> buffering to memory, as our fastest solution now would be to keep what we
> done and just handle the upload in a seperate module.
>
> Thanks
>
> Imad
>
> "David Wang"  wrote in message
>
> news:a7d1bce2-cfbb-4f82-9cdd-88b5f8829acd@p39g2000prm.googlegroups.com...
> Sorry, I really do not use ATL nor know where it is supported.
>
> Personally, I don't see a need to use ATL if you are just writing
> plain ISAPI. And the proper way to support large uploads is NOT to
> buffer the entire thing to memory (which is what you observe) but to
> stream, and you'll need to code that.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Apr 25, 9:43 am, "Imad"  wrote:
>
>
>
> > Thank you for your reply,
> > i have created a pure ISAPI upload and it worked for over 65MB uploads 
> > on
> > IIS6 on the same server,
> > so thats confirmed that its an ATL problem under IIS6 because the same 
> > app
> > works fine under IIS7,
> > i have already posted my problem in the atl newsgroup because i wasnt 
> > sure
> > weather it was an iis or atl problem but havent got a reply, do you know
> > where i can post to find answers as to if there is a solution around it 
> > to
> > make atl server based ISAPI upload larger than 65MB under IIS6?
>
> > Thanks
>
> > Imad
>
> > "David Wang"  wrote in message
>
> >news:b6830a63-59bf-4334-80ba-4ae3ed889b32@w5g2000prd.googlegroups.com...
> > I understand the pressure you are under. Most people posting questions
> > tend to be under some sort of pressure.
>
> > I don't know ATL Server well enough to configure it. I always write
> > pure ISAPI code and never use things like ATL Server.
>
> > I can only tell you that ISAPI and IIS itself does not have such
> > upload size limit. If you are encountering limits, it is either in ATL
> > Server (the layer on top of ISAPI that you are using) or something in
> > the network connectivity layer underneath IIS. Usually people remember
> > configuring such limits in the network layer, so I say it's in ATL.
>
> > No matter what, the client must also verify that their production
> > environment, including the production server and its network, load
> > balancer, proxy servers, etc are not throttling requests anywhere,
> > even inadvertently, and can support posts >64MB.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //
>
> > On Apr 18, 8:23 am, "Imad"  wrote:
>
> > > sorry, posted to sender instead of to group by mistake and was 
> > > wondering
> > > why
> > > it was taking long to appear, will repost to group.
>
> > > are you absolutely sure that the atl server wont allow uploads for 
> > > files
> > > larger than 65MB?
> > > because we have a big problem, when we started building the site and
> > > recommended this platform there was no limitation of such kind 
> > > mentioned
> > > anywhere on microsoft msdn or in the documentations, now we have an
> > > angry
> > > customer that cannot wait for us to rebuild his site (that took us 6
> > > months
> > > and 4 developers to build with atl so you can imagine our loss if we
> > > were
> > > to
> > > rebuild) and not being able to upload large files is not acceptable 
> > > for
> > > him.
> > > please i need a solution for this, if you cannot give me answers 
> > > please
> > > direct me if you can.
>
> > > Thanks
>
> > > Imad
>
> > > "David Wang"  wrote in message
>
> > >news:6815dee0-259e-4817-92e0-8e364e99b1c2@m73g2000hsh.googlegroups.com...
> > > Just build a plain Win32 DLL which exports GetExtensionVersion and
> > > HttpExtensionProc. No special solution necessary.
>
> > >http://blogs.msdn.com/david.wang/archive/2006/03/25/MFC-ISAPI-Templat...
>
> > >http://blogs.msdn.com/david.wang/archive/2005/12/19/HOWTO-Compile-and...
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > //
>
> > > On Apr 16, 6:08 am, "Imad"  wrote:
>
> > > > but if it was atl limitation it would also be limited under IIS7?
> > > > what kind of solution do you choose in VS2005 for pure ISAPI
> > > > extension?
>
> > > > Imad
>
> > > > "David Wang"  wrote in message
>
> > > >news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com...
> > > > On Apr 15, 7:03 am, "Imad"  wrote:
>
> > > > > Hi,
> > > > > i have written a web app using ATL server, it has file upload that
> > > > > is
> > > > > working great on the test machine which is vista with IIS7, but it
> > > > > doesnt
> > > > > uplad files larger than about 65MB on the production or any 
> > > > > windows
> > > > > 2003
> > > > > server with IIS6, note that i have asp.net applications running on
> > > > > that
> > > > > 2k3
> > > > > server that are uploading larger files no problems.
> > > > > what happens is the w3wp.exe remains the same size in memory and 
> > > > > the
> > > > > server
> > > > > closes the connection instantly and the client detects that after 
> > > > > 5
> > > > > minutes,
> > > > > but when the file is less than 65MB the w3wp.exe increases in 
> > > > > memory
> > > > > size
> > > > > as
> > > > > much as the uploaded file size and the file is uploaded.
> > > > > i have ovewritten the 2 form upload related functions as follows 
> > > > > in
> > > > > the
> > > > > handler .h:
> > > > > inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> > > > > inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> > > > > and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is
> > > > > equals
> > > > > to
> > > > > 1GB.
> > > > > the web app is configured to have its own app pool that has all
> > > > > default
> > > > > settings.
>
> > > > > any ideas why? i have found people with same problem but i couldnt
> > > > > find
> > > > > a
> > > > > solution for it anywhere on
> > > > > the net, and am not sure if its caused by IIS or ATL.
>
> > > > > Thanks
>
> > > > It has to be ATL limitation.
>
> > > > ASP.Net is an ISAPI Extension on wrapper on managed code IIS which 
> > > > you
> > > > say has no such limitation.
> > > > ATL Server is another ISAPI Extension wrapper on IIS which you say 
> > > > has
> > > > such limitation.
> > > > I have my pure ISAPI Extension to accept POSTed uploads which has no
> > > > such limitation.
>
> > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > > //- Hide quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

To me, when you say:

"any web designer can change the layout of the site with html code
only"

That pretty much satisfies any server-side application platform
because by definition if you can change the HTML rendered by the
client browser, you can change its layout.

Broadly speaking, ASP, ASP.Net, ATL, PHP, etc are all essentially
textual script files that can be eventually parsed by some engine to
produce HTML which is rendered by a client browser.

ATL SRF files are essentially customized scripting language, predating
ASP, embedded in a document that eventually becomes HTML. It gives
stronger hooks to invoke the "ISAPI" half of ATL from the SRF but
nothing that ASP or ASP.Net cannot match via Server.Execute or simple
#include. In essence, I view ATL as the old way of doing things.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Apr 28, 4:25 am, "Imad"  wrote:
> am actually surprised of you thinking this way, are we talking about the
> same thing? in vs2005 you choose atl server project. still when it comes to
> speed of development i'de say asp.net is quicker, but we needed a platform> where whenever a html change was wanted (which is on daily basis) the client
> would be able to do because they have a full time html designer who only
> knows to copy and paste something like {{getsomdatafromisapiatlfunction}} to
> position the data wherever he wants on the page, with asp.net they would
> have had to come back to us to change.
> most of our work is done using asp.net because its very stable, it does
> exactly what its asked to do, and its the quickest to get a web app up and> running but unfortunatly for that solution it wasnt, i know we could do
> things to get around that like creating html templates where the client can
> edit but didnt see the need since it already existed in atl and we all have
> experience in c so we had no problems doing things quick enough with atl> server type of solution.
>
> Thanks
>
> Imad
>
> "David Wang"  wrote in message
>
> news:628497a8-48ad-4ee5-88b8-63088a8c9598@i36g2000prf.googlegroups.com...
> I find it interesting that you say ATL gives speed of development
> because when I think "speed of development", I think of ASP.Net and
> Visual Web Developer or even ASP/PHP. ATL/MFC predates those
> technologies and in comparison to those later technologies, it only
> provides the bare basics. One main difference is that ATL is in native
> code instead of managed or interpreted code like ASP.Net or ASP.
> Hence, I find it interesting that you say native code gives you speed
> of development because most people would say otherwise. Unless you
> only have ATL experts and not ASP/ASP.Net experts on hand. ASP.Net
> Master Pages exceeds everything you said were advantages in ATL, and
> then some.
>
> Sorry, I don't have that sample code at hand, but I know it can be
> done. with asynchronous IO to not tie up any threads. You should not
> have trouble with this task if ATL gives you speed of development.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Apr 27, 10:05 am, "Imad"  wrote:
>
>
>
> > large file upload is just a small but important role of that website.
> > why we chose atl is speed of development and the fact that any web
> > designer
> > can change the layout of the site with html code only.
> > atl already implements session, cookies and oledb connections to say the> > least so we would have had to reinvent the wheel if working with pure
> > ISAPI
> > but of course we didnt know about the limitation of file uploads at the
> > time
> > as it wasnt mentionned anywhere.
> > do you have a link for a sample of pure ISAPI upload to stream rather than
> > buffering to memory, as our fastest solution now would be to keep what we
> > done and just handle the upload in a seperate module.
>
> > Thanks
>
> > Imad
>
> > "David Wang"  wrote in message
>
> >news:a7d1bce2-cfbb-4f82-9cdd-88b5f8829acd@p39g2000prm.googlegroups.com...> > Sorry, I really do not use ATL nor know where it is supported.
>
> > Personally, I don't see a need to use ATL if you are just writing
> > plain ISAPI. And the proper way to support large uploads is NOT to
> > buffer the entire thing to memory (which is what you observe) but to
> > stream, and you'll need to code that.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //
>
> > On Apr 25, 9:43 am, "Imad"  wrote:
>
> > > Thank you for your reply,
> > > i have created a pure ISAPI upload and it worked for over 65MB uploads> > > on
> > > IIS6 on the same server,
> > > so thats confirmed that its an ATL problem under IIS6 because the same> > > app
> > > works fine under IIS7,
> > > i have already posted my problem in the atl newsgroup because i wasnt
> > > sure
> > > weather it was an iis or atl problem but havent got a reply, do you know
> > > where i can post to find answers as to if there is a solution around it
> > > to
> > > make atl server based ISAPI upload larger than 65MB under IIS6?
>
> > > Thanks
>
> > > Imad
>
> > > "David Wang"  wrote in message
>
> > >news:b6830a63-59bf-4334-80ba-4ae3ed889b32@w5g2000prd.googlegroups.com..> > > I understand the pressure you are under. Most people posting questions> > > tend to be under some sort of pressure.
>
> > > I don't know ATL Server well enough to configure it. I always write
> > > pure ISAPI code and never use things like ATL Server.
>
> > > I can only tell you that ISAPI and IIS itself does not have such
> > > upload size limit. If you are encountering limits, it is either in ATL> > > Server (the layer on top of ISAPI that you are using) or something in
> > > the network connectivity layer underneath IIS. Usually people remember> > > configuring such limits in the network layer, so I say it's in ATL.
>
> > > No matter what, the client must also verify that their production
> > > environment, including the production server and its network, load
> > > balancer, proxy servers, etc are not throttling requests anywhere,
> > > even inadvertently, and can support posts >64MB.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > //
>
> > > On Apr 18, 8:23 am, "Imad"  wrote:
>
> > > > sorry, posted to sender instead of to group by mistake and was
> > > > wondering
> > > > why
> > > > it was taking long to appear, will repost to group.
>
> > > > are you absolutely sure that the atl server wont allow uploads for
> > > > files
> > > > larger than 65MB?
> > > > because we have a big problem, when we started building the site and> > > > recommended this platform there was no limitation of such kind
> > > > mentioned
> > > > anywhere on microsoft msdn or in the documentations, now we have an
> > > > angry
> > > > customer that cannot wait for us to rebuild his site (that took us 6> > > > months
> > > > and 4 developers to build with atl so you can imagine our loss if we> > > > were
> > > > to
> > > > rebuild) and not being able to upload large files is not acceptable
> > > > for
> > > > him.
> > > > please i need a solution for this, if you cannot give me answers
> > > > please
> > > > direct me if you can.
>
> > > > Thanks
>
> > > > Imad
>
> > > > "David Wang"  wrote in message
>
> > > >news:6815dee0-259e-4817-92e0-8e364e99b1c2@m73g2000hsh.googlegroups.com...
> > > > Just build a plain Win32 DLL which exports GetExtensionVersion and
> > > > HttpExtensionProc. No special solution necessary.
>
> > > >http://blogs.msdn.com/david.wang/archive/2006/03/25/MFC-ISAPI-Templat> > > >http://blogs.msdn.com/david.wang/archive/2005/12/19/HOWTO-Compile-and> > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > > //
>
> > > > On Apr 16, 6:08 am, "Imad"  wrote:
>
> > > > > but if it was atl limitation it would also be limited under IIS7?
> > > > > what kind of solution do you choose in VS2005 for pure ISAPI
> > > > > extension?
>
> > > > > Imad
>
> > > > > "David Wang"  wrote in message
>
> > > > >news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com...
> > > > > On Apr 15, 7:03 am, "Imad"  wrote:
>
> > > > > > Hi,
> > > > > > i have written a web app using ATL server, it has file upload that
> > > > > > is
> > > > > > working great on the test machine which is vista with IIS7, but it
> > > > > > doesnt
> > > > > > uplad files larger than about 65MB on the production or any
> > > > > > windows
> > > > > > 2003
> > > > > > server with IIS6, note that i have asp.net applications running on
> > > > > > that
> > > > > > 2k3
> > > > > > server that are uploading larger files no problems.
> > > > > > what happens is the w3wp.exe remains the same size in memory and> > > > > > the
> > > > > > server
> > > > > > closes the connection instantly and the client detects that after
> > > > > > 5
> > > > > > minutes,
> > > > > > but when the file is less than 65MB the w3wp.exe increases in
> > > > > > memory
> > > > > > size
> > > > > > as
> > > > > > much as the uploaded file size and the file is uploaded.
> > > > > > i have ovewritten the 2 form upload related functions as follows> > > > > > in
> > > > > > the
> > > > > > handler .h:
> > > > > > inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> > > > > > inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> > > > > > and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is
> > > > > > equals
> > > > > > to
> > > > > > 1GB.
> > > > > > the web app is configured to have its own app pool that has all
> > > > > > default
> > > > > > settings.
>
> > > > > > any ideas why? i have found people with same problem but i couldnt
> > > > > > find
> > > > > > a
> > > > > > solution for it anywhere on
> > > > > > the net, and am not sure if its caused by IIS or ATL.
>
> > > > > > Thanks
>
> > > > > It has to be ATL limitation.
>
> > > > > ASP.Net is an ISAPI Extension on wrapper on managed code IIS which> > > > > you
> > > > > say has no such limitation.
> > > > > ATL Server is another ISAPI Extension wrapper on IIS which you say> > > > > has
> > > > > such limitation.
> > > > > I have my pure ISAPI Extension to accept POSTed uploads which has no
> > > > > such limitation.
>
> > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > > > //- Hide quoted text -
>
> > > > > - Show quoted text -- Hide quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

I agree to anyone can change on any the platforms you mentionned, and 
asp.net is definitly faster in development as a simple example you enable 
control state and you dont do code to loop thru forms and repopulate your 
controls after submission, but if you give that .aspx page to a web designer 
who has no experience in anything other than html code and he changes you 
control's name from textfield1 to text1 and your code doesnt find the value 
anymore then you have a problem, so to prevent that you need to hide 
anything you use in code and maybe write controls dynamicaly so you lost 
part of the speed of development and you're probably down to the atl speed 
of development after a couple of potential problems like this one.
asp and php are not faster than atl, and am not sure about the exact history 
of php but i dont think its newer technology than atl but still prefferred 
platform to a lot of people so new or old technology doesnt really matter as 
long as its suitable for your needs.
i dont want to be defending atl as i also dont think its the greatest but 
all of them have pros and cons, but am thinking maybe there are more 
problems with atl than we know of since that not only its not being 
recommended as to at least this thread but also going to be NOT supported in 
future MS visual studio environments? the file upload issue is 1 problem 
that i had but another that i havent posted because i found a way around it 
is that am using database connection cache, and in application pool in IIS 
if i leave recycle worker process in minutes to default which is 1740, the 
MySql connections reaches its limit which is 20,000 in no time and i start 
getting connection to database errors, so it doesnt seem to me as if its 
reusing those connections but just keeping them open, i got around that 
problem by making that setting 360 minutes, am not sure if thats the ideal 
workaround when we have more hits on that site but its working for now.

Imad



"David Wang"  wrote in message 
news:fe5678f0-2239-488b-b8dd-bf311bb7f461@r9g2000prd.googlegroups.com...
To me, when you say:

"any web designer can change the layout of the site with html code
only"

That pretty much satisfies any server-side application platform
because by definition if you can change the HTML rendered by the
client browser, you can change its layout.

Broadly speaking, ASP, ASP.Net, ATL, PHP, etc are all essentially
textual script files that can be eventually parsed by some engine to
produce HTML which is rendered by a client browser.

ATL SRF files are essentially customized scripting language, predating
ASP, embedded in a document that eventually becomes HTML. It gives
stronger hooks to invoke the "ISAPI" half of ATL from the SRF but
nothing that ASP or ASP.Net cannot match via Server.Execute or simple
#include. In essence, I view ATL as the old way of doing things.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Apr 28, 4:25 am, "Imad"  wrote:
> am actually surprised of you thinking this way, are we talking about the
> same thing? in vs2005 you choose atl server project. still when it comes 
> to
> speed of development i'de say asp.net is quicker, but we needed a platform
> where whenever a html change was wanted (which is on daily basis) the 
> client
> would be able to do because they have a full time html designer who only
> knows to copy and paste something like {{getsomdatafromisapiatlfunction}} 
> to
> position the data wherever he wants on the page, with asp.net they would
> have had to come back to us to change.
> most of our work is done using asp.net because its very stable, it does
> exactly what its asked to do, and its the quickest to get a web app up and
> running but unfortunatly for that solution it wasnt, i know we could do
> things to get around that like creating html templates where the client 
> can
> edit but didnt see the need since it already existed in atl and we all 
> have
> experience in c++ so we had no problems doing things quick enough with atl
> server type of solution.
>
> Thanks
>
> Imad
>
> "David Wang"  wrote in message
>
> news:628497a8-48ad-4ee5-88b8-63088a8c9598@i36g2000prf.googlegroups.com...
> I find it interesting that you say ATL gives speed of development
> because when I think "speed of development", I think of ASP.Net and
> Visual Web Developer or even ASP/PHP. ATL/MFC predates those
> technologies and in comparison to those later technologies, it only
> provides the bare basics. One main difference is that ATL is in native
> code instead of managed or interpreted code like ASP.Net or ASP.
> Hence, I find it interesting that you say native code gives you speed
> of development because most people would say otherwise. Unless you
> only have ATL experts and not ASP/ASP.Net experts on hand. ASP.Net
> Master Pages exceeds everything you said were advantages in ATL, and
> then some.
>
> Sorry, I don't have that sample code at hand, but I know it can be
> done. with asynchronous IO to not tie up any threads. You should not
> have trouble with this task if ATL gives you speed of development.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Apr 27, 10:05 am, "Imad"  wrote:
>
>
>
> > large file upload is just a small but important role of that website.
> > why we chose atl is speed of development and the fact that any web
> > designer
> > can change the layout of the site with html code only.
> > atl already implements session, cookies and oledb connections to say the
> > least so we would have had to reinvent the wheel if working with pure
> > ISAPI
> > but of course we didnt know about the limitation of file uploads at the
> > time
> > as it wasnt mentionned anywhere.
> > do you have a link for a sample of pure ISAPI upload to stream rather 
> > than
> > buffering to memory, as our fastest solution now would be to keep what 
> > we
> > done and just handle the upload in a seperate module.
>
> > Thanks
>
> > Imad
>
> > "David Wang"  wrote in message
>
> >news:a7d1bce2-cfbb-4f82-9cdd-88b5f8829acd@p39g2000prm.googlegroups.com...
> > Sorry, I really do not use ATL nor know where it is supported.
>
> > Personally, I don't see a need to use ATL if you are just writing
> > plain ISAPI. And the proper way to support large uploads is NOT to
> > buffer the entire thing to memory (which is what you observe) but to
> > stream, and you'll need to code that.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //
>
> > On Apr 25, 9:43 am, "Imad"  wrote:
>
> > > Thank you for your reply,
> > > i have created a pure ISAPI upload and it worked for over 65MB uploads
> > > on
> > > IIS6 on the same server,
> > > so thats confirmed that its an ATL problem under IIS6 because the same
> > > app
> > > works fine under IIS7,
> > > i have already posted my problem in the atl newsgroup because i wasnt
> > > sure
> > > weather it was an iis or atl problem but havent got a reply, do you 
> > > know
> > > where i can post to find answers as to if there is a solution around 
> > > it
> > > to
> > > make atl server based ISAPI upload larger than 65MB under IIS6?
>
> > > Thanks
>
> > > Imad
>
> > > "David Wang"  wrote in message
>
> > >news:b6830a63-59bf-4334-80ba-4ae3ed889b32@w5g2000prd.googlegroups.com...
> > > I understand the pressure you are under. Most people posting questions
> > > tend to be under some sort of pressure.
>
> > > I don't know ATL Server well enough to configure it. I always write
> > > pure ISAPI code and never use things like ATL Server.
>
> > > I can only tell you that ISAPI and IIS itself does not have such
> > > upload size limit. If you are encountering limits, it is either in ATL
> > > Server (the layer on top of ISAPI that you are using) or something in
> > > the network connectivity layer underneath IIS. Usually people remember
> > > configuring such limits in the network layer, so I say it's in ATL.
>
> > > No matter what, the client must also verify that their production
> > > environment, including the production server and its network, load
> > > balancer, proxy servers, etc are not throttling requests anywhere,
> > > even inadvertently, and can support posts >64MB.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > //
>
> > > On Apr 18, 8:23 am, "Imad"  wrote:
>
> > > > sorry, posted to sender instead of to group by mistake and was
> > > > wondering
> > > > why
> > > > it was taking long to appear, will repost to group.
>
> > > > are you absolutely sure that the atl server wont allow uploads for
> > > > files
> > > > larger than 65MB?
> > > > because we have a big problem, when we started building the site and
> > > > recommended this platform there was no limitation of such kind
> > > > mentioned
> > > > anywhere on microsoft msdn or in the documentations, now we have an
> > > > angry
> > > > customer that cannot wait for us to rebuild his site (that took us 6
> > > > months
> > > > and 4 developers to build with atl so you can imagine our loss if we
> > > > were
> > > > to
> > > > rebuild) and not being able to upload large files is not acceptable
> > > > for
> > > > him.
> > > > please i need a solution for this, if you cannot give me answers
> > > > please
> > > > direct me if you can.
>
> > > > Thanks
>
> > > > Imad
>
> > > > "David Wang"  wrote in message
>
> > > >news:6815dee0-259e-4817-92e0-8e364e99b1c2@m73g2000hsh.googlegroups.com...
> > > > Just build a plain Win32 DLL which exports GetExtensionVersion and
> > > > HttpExtensionProc. No special solution necessary.
>
> > > >http://blogs.msdn.com/david.wang/archive/2006/03/25/MFC-ISAPI-Templat...
>
> > > >http://blogs.msdn.com/david.wang/archive/2005/12/19/HOWTO-Compile-and...
>
> > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > > //
>
> > > > On Apr 16, 6:08 am, "Imad"  wrote:
>
> > > > > but if it was atl limitation it would also be limited under IIS7?
> > > > > what kind of solution do you choose in VS2005 for pure ISAPI
> > > > > extension?
>
> > > > > Imad
>
> > > > > "David Wang"  wrote in message
>
> > > > >news:891b2c61-8572-458b-a39c-f38e0d033114@b5g2000pri.googlegroups.com...
> > > > > On Apr 15, 7:03 am, "Imad"  wrote:
>
> > > > > > Hi,
> > > > > > i have written a web app using ATL server, it has file upload 
> > > > > > that
> > > > > > is
> > > > > > working great on the test machine which is vista with IIS7, but 
> > > > > > it
> > > > > > doesnt
> > > > > > uplad files larger than about 65MB on the production or any
> > > > > > windows
> > > > > > 2003
> > > > > > server with IIS6, note that i have asp.net applications running 
> > > > > > on
> > > > > > that
> > > > > > 2k3
> > > > > > server that are uploading larger files no problems.
> > > > > > what happens is the w3wp.exe remains the same size in memory and
> > > > > > the
> > > > > > server
> > > > > > closes the connection instantly and the client detects that 
> > > > > > after
> > > > > > 5
> > > > > > minutes,
> > > > > > but when the file is less than 65MB the w3wp.exe increases in
> > > > > > memory
> > > > > > size
> > > > > > as
> > > > > > much as the uploaded file size and the file is uploaded.
> > > > > > i have ovewritten the 2 form upload related functions as follows
> > > > > > in
> > > > > > the
> > > > > > handler .h:
> > > > > > inline DWORD FormFlags(void) { return ATL_FORM_FLAG_NONE; }
> > > > > > inline DWORD MaxFormSize(void) { return MAX_FORM_SIZE; }
> > > > > > and MAX_FORM_SIZE is defined in stdafx.h as 1073741824 which is
> > > > > > equals
> > > > > > to
> > > > > > 1GB.
> > > > > > the web app is configured to have its own app pool that has all
> > > > > > default
> > > > > > settings.
>
> > > > > > any ideas why? i have found people with same problem but i 
> > > > > > couldnt
> > > > > > find
> > > > > > a
> > > > > > solution for it anywhere on
> > > > > > the net, and am not sure if its caused by IIS or ATL.
>
> > > > > > Thanks
>
> > > > > It has to be ATL limitation.
>
> > > > > ASP.Net is an ISAPI Extension on wrapper on managed code IIS which
> > > > > you
> > > > > say has no such limitation.
> > > > > ATL Server is another ISAPI Extension wrapper on IIS which you say
> > > > > has
> > > > > such limitation.
> > > > > I have my pure ISAPI Extension to accept POSTed uploads which has 
> > > > > no
> > > > > such limitation.
>
> > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > > > //- Hide quoted text -
>
> > > > > - Show quoted text -- Hide quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -