You probably can't even fit the process scheduler of a modern OS in 64k. Unless you want to code your apps on bare metal (no OS) assembly language, there is no way you'll get any higher level language in 64k. Even then, toss out the notions of a database, transactions, concurrency, and performance.
On Feb 11, 5:30 am, raven <ravenspo...@yahoo.com> wrote: > It seems that everyone is running with Apache and gobs of memory > available. They cannot really get their heads around running web2py > out of the box in 64K. > > So let me explain why this is important. > > When I sell a desktop application to someone, all they have to pay for > is my coding work. They already have a machine to run it on, and they > are used to maintaining it. > > Selling a web application is rather different. The buyer has to pay > for the monthly rental of each K of memory and maintaining a remote > unix server is intimidating > > My customers do not require giant websites with thousands of users, > just small database applications that a few employees can access while > they are on the road. > > So I want to be able to offer web2py running out of the box in 64K, as > a simple, cost-effective solution. > > On Feb 10, 10:40 am, raven <ravenspo...@yahoo.com> wrote: > > > web2py is working very well for me on my MSWINDOWS desktop. > > > I am ready to deploy my first application on a virtual private server > > running Ubuntu with 64K of guaranteed RAM > > > I loaded the web2py source and typed > > > python2.5 web2py.py > > > and immediatly ran out of memory. > > > How much memory do I need to purchase? -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
