#1 yeah... #2 yeah,i think.. and InboundPollingThread to cover because some modem (or Comm port like me) didn't send signal generated to notify new message.. so we must manually check it..
On 5 Jan, 21:20, Peogrammer Base <[email protected]> wrote: > hi all, > thanks Thanasis ,Taufik Fahrudin , Pietro > > #.1 > *critical section* was handled by databases (like MySQL and SQLServer > and Oracle) . > Because that databases can use at multiple user (or two therads) > > #.2 **InboundPollingThread ** > i think smslib cannot detect all new message (lost some *+CMTI:* > recived in the process) therefore *InboundPollingThread * cover this > issue. > is this correct? > > #.3 > Access is a very bad DB because i think Access cannot work > *concurrent* with two threads. > > On 1/3/10, Peogrammer Base <[email protected]> wrote: > > > > > thanks Thanasis ,Taufik Fahrudin , Pietro > > > On 1/3/10, Thanasis <[email protected]> wrote: > >> Hello, > > >> By "Async mode" you refer to the signals generated from the modem when > >> you receive a new message? > > >> On Jan 3, 1:38 pm, Taufik Fahrudin <[email protected]> wrote: > >> Yeah,not all modem support async mode. > > >> -- > > >> You received this message because you are subscribed to the Google Groups > >> "SMSLib for Java User Group" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]. > >> For more options, visit this group at > >>http://groups.google.com/group/smslib?hl=en.
-- You received this message because you are subscribed to the Google Groups "SMSLib for Java User Group" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/smslib?hl=en.
