RE: Running Communication Process in the background

2008-07-01 Thread Tam Hanna 
Hi,
sorry for the short reply:

Use a state machine that handles the protocol. Then, fire an alarm
frequently and run the state machine.

All the best
Tam Hanna


Subject: Running Communication Process in the background
From: "Mukesh Singh" <[EMAIL PROTECTED]>
Date: Sat, 28 Jun 2008 14:30:02 -0700
X-Message-Number: 1

Hi All,

First of all let me explain what is my application requirement:

1. Networking based application which send request to a particular server
and receive the response.
2. The server is also capable to send push mechanism to inform us that there
is something new with the server and we (client) need to sync with it, for
that we have to register our application for the incoming SMS.

Now, I wanted to achieve following:

1. When my application is not running and I got a new SMS from the server to
sync, I wanted to launch our application silently (without any UI) to access
all my request creation and networking related functions and data structure,
so that I can easily create the request, send it over networking channel and
get the response from the server, store it to my data structures and than
close my application.

2. After completion of this task, I wanted show an attention to the user
that you have received something new.

3. And at last kill the process without user intervention.

I tried several things like launch codes and launch flags with the
SysAppLaunch function but couldn't get much success with that.

Can any body give some fare idea, how to achieve this thing. One more thing
I wanted to inform that I have looked into some application and they are
actually working very silently in the background without affecting the other
application and when you launch those application you can easily watch an
update from the last launch. So running application in the background is
possible that is for sure.

Waiting for a positive reply.

Thanks
Mukesh Singh



-- 
For information on using the ACCESS Developer Forums, or to unsubscribe, please 
see http://www.access-company.com/developers/forums/

Re: MemPtrNew fragmentation

2008-07-01 Thread Lionscribe 
Well this calls for the good old fashioned method of seperate records for each 
index. The cost of 16-18 bytes per record will pale in comparison to the 100+ 
bytes saved per record. You can then use all the Dm* functions for sorting and 
etc.
Lionscribe

-- 
For information on using the ACCESS Developer Forums, or to unsubscribe, please 
see http://www.access-company.com/developers/forums/

Re: MemPtrNew fragmentation

2008-07-01 Thread Michal Seliga 

John Gruenenfelder wrote:


Unfortunately, at 308 bytes per item, the index is limited to ~210 total items
before the 64K allocation limit is reached.



forget about limit, you can use MemGluePtrNew from glue library with which you 
can allocate more then 64kb in one block and it works from palmos 3.5


or you can use code taken from pdn.palm.com, its setting of some flags, it also 
allows you to allocate more then 64kb in one block


and you also can store such big blocks as resources or records in databases, 
problem is that with such databases hotsync will fail so backup with hotsync, 
pilot-tools etc. is not possible


--
For information on using the ACCESS Developer Forums, or to unsubscribe, please 
see http://www.access-company.com/developers/forums/