Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Compact Framework / April 2006

Tip: Looking for answers? Try searching our database.

Multi-tier programming on devices

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jon Brunson - 03 Apr 2006 14:42 GMT
Howdy all,

Is it advisable to write Mobile Device applications using multi-tier
methodology? Or as Devices are much more resource-limited, would keeping
the number of tiers help reduce memory and processor usage?

I know apps on Devices can only use a maximum of 32MB of RAM, and
unfortunately our app is approaching, and at a push can be made to
breach that 32MB barrier. It's written in VB.NET, and has 4 tiers:-

1. GUI
2. Business logic
3. SqlCe interface
4. SqlServer interface

If we squished the number of layers from 4 down to 2 (GUI & "Everything
else"), would this help things memory-wise?
<ctacke/> - 03 Apr 2006 15:53 GMT
Pushing it to a single tier would likely gain nothing in memory usage.  It's
also not true that you have a 32MB hard limit.  The CF does a lot of
allocation from shared space. You have a 32MB virtual space limit per
process.

-Chris

> Howdy all,
>
[quoted text clipped - 13 lines]
> If we squished the number of layers from 4 down to 2 (GUI & "Everything
> else"), would this help things memory-wise?
Jon Brunson - 03 Apr 2006 16:04 GMT
Surely if an app is the first (or perhaps only) .NET app on the device,
the CF would be using that app's memory space for the framework, or does
the CF somehow create it's own process along side your own to run in?

> Pushing it to a single tier would likely gain nothing in memory usage.  It's
> also not true that you have a 32MB hard limit.  The CF does a lot of
[quoted text clipped - 20 lines]
>> If we squished the number of layers from 4 down to 2 (GUI & "Everything
>> else"), would this help things memory-wise?
<ctacke/> - 03 Apr 2006 16:30 GMT
The CF runs partly in slot 0, partly in slot 1 and partly in shared memory
space.  Read all 3 parts of this, along with Mike Zintel's linked blog
entry:

http://blogs.msdn.com/stevenpr/archive/2005/12/14/503818.aspx

-Chris

> Surely if an app is the first (or perhaps only) .NET app on the device,
> the CF would be using that app's memory space for the framework, or does
[quoted text clipped - 24 lines]
>>> If we squished the number of layers from 4 down to 2 (GUI & "Everything
>>> else"), would this help things memory-wise?
Jon Brunson - 03 Apr 2006 17:06 GMT
Thanks Chris

> The CF runs partly in slot 0, partly in slot 1 and partly in shared memory
> space.  Read all 3 parts of this, along with Mike Zintel's linked blog
[quoted text clipped - 32 lines]
>>>> If we squished the number of layers from 4 down to 2 (GUI & "Everything
>>>> else"), would this help things memory-wise?

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.