Re: Using SQl to store aspx pages and memory problems

Tech-Archive recommends: Fix windows errors by optimizing your registry

why are are you doing this ? This is not a good design. I'm surprised itr
works at all .

Just use use regular aspx files and be done with it.




"matvdl" <matvdl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AAA1B336-8604-4D0B-B50C-2BAD27ACF9E5@xxxxxxxxxxxxxxxx
> Many of the pages have server side code - they are aspx files - not html
> files. e.g some of the files may need to get information such as current
> date the file was displayed - or they are customized based on the browser
> that views them - so they get modifed at run-time. Many have server side
> controls that display charts. (chartfx control)
>
> The way I manage this is to write the saved aspx file to a temp directory
> on
> the server and redirect the request to this file.
>
> I also have html files that are retrieved from SQL but these are simply
> written back to the client - the problem is with aspx files.
>
> Any help would be appreciated.
>
> Matthew
> --
> matthew
>
>
> "TJS" wrote:
>
>> what exactly does this mean ?
>>
>> "as each page is requested it is retrieved from SQL saved to the
>> temp directory and compiled "
>>
>> why are you saving it twice ?
>>
>> if it 's saved in sql why not just write it back to the client?
>>
>>
>>
>> "matvdl" <matvdl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:753E0555-B034-40F7-BD3A-E3EE61600EA0@xxxxxxxxxxxxxxxx
>> >I have a system that was originally developed in asp - the pages are
>> >saved
>> >in
>> > SQL (there are over 10,000 pages) and saved to a temp directory in the
>> > server
>> > when requested by a client.
>> >
>> > I have updated this system and changed the pages that are saved to the
>> > server as aspx - everything works fine and pages can be served - but
>> >
>> > Its not impossible for a single client to request 100 plus pages in one
>> > session - as each page is requested it is retrieved from SQL saved to
>> > the
>> > temp directory and compiled - problems are.
>> > - Performance is well down on the original asp system - I believe
>> > that
>> > this due to the compiling of the pages in asp.net
>> > - The memory usage of server also goes through the roof - there is a
>> > considerable increase in memory as each page is loaded
>> >
>> > Are there any solutions to these problems??
>> >
>> > --
>> > matthew
>>
>>
>>


.

Relevant Pages

  • Re: breaking the model
    ... > The forms data then is in the Request object. ... HTTP Request; in this case, the form POST Request from the Page. ... client and server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Resolving record with enumerated type
    ... In a CPU BFM package, ... because data goes in two directions (request from the ... from the server to the client), you'll need some way to orchestrate ...
    (comp.lang.vhdl)
  • Re: NadaNet file server coming soon...
    ... Applesoft BASIC running under ProDOS, in less than 300 lines, ... After each command is completed by the server, ... client the result code, the AUX TYPE, ... forgoes queueing (since one client can't have more than one request ...
    (comp.sys.apple2)
  • Re: Kerberos with Windows Integrated authentication
    ... behaviour if your Web server is in the client broweser's Internet zone. ... referencing it by computer name rather than FQDN), the browser will request ... Obviously, if you want to use Kerberos for authentication, you will either ...
    (microsoft.public.windows.server.security)
  • Re: Performance Issue with Runtime Image
    ... >> the client, closes the connection, then dies. ... request before even accepting the next incoming connection. ... The client program is unaffected so presumably the server is ...
    (comp.lang.smalltalk.dolphin)