J2ME:Sharing RMS between threads

[timnels]

I have a timer task that is getting GPS settings at a pre-defined
interval and storing them in RMS. I have another thread that will be
picking those entries up and pushing them up to a server on the
Internet. From what I have read accessing these without a
syncronization method is a no-no. What methods are people using to
syncronize access to RMS? Also, is there a simple way to re-use record
ID's so your RMS doesn't grow out of control?
Thanks.

 

[jan V]

I have a timer task that is getting GPS settings at a pre-defined

interval and storing them in RMS.

What's RMS?

 

[timnels]

The J2ME/MIDP data storage class.

 

[jan V]

I have a timer task that is getting GPS settings at a pre-defined
interval and storing them in RMS.

Thanks for clarifying what RMS is.

I have another thread that will be
picking those entries up and pushing them up to a server on the
Internet. From what I have read accessing these without a
syncronization method is a no-no. What methods are people using to
syncronize access to RMS?

If the RMS doesn't provide some locking, i.e. synchronization, service
itself, then you could use a plain Object to represent the RMS lock. As long
as both producer and consumer sides of your architecture would "go through"
(i.e. honour the lock semantics) the lock, then your records would never get
corrupted or read partially. Using a plain Object with Java's thread
snchronization support (wait/notify etc) is rather elementary...

Also, is there a simple way to re-use record
ID's so your RMS doesn't grow out of control?

Circular list? Pool of IDs? I've got no experience of the J2ME platform, so
maybe these suggestions are not feasible on such a restricted JVM.