RE: AT parsing

> -----Original Message-----
> From: Rene Kluwen / Chimit Software Solutions 

> At this moment, each function implements its own AT parsing, 
> most of it
> is done (rudimentarily) in at2_wait_modem_command.
> Would Kannel benefit from a general AT responses/indications parser?
> 
> I am thinking of something like:
> 
> /* this function takes a AT response or indication and returns the
>  * parameters as an Octstr-list.
>  * returns 0 on success or -1 on error.
>  */
> int at2_parse_at(Octstr *line, List **result)
> {
>     ...
> }
> But any other result parameters that can be easily used in a calling
> function is also good for me ;)...

I think it will only make sense if you do very general parsing while accepting "special cases" (of course), and then used it as a "message dispatch" to invoke a set of some sort of at2_<notification type>_parse() functions. if no such drastic chage is planned, then we may as well stick with what we have.

--
Oded Arbel
m-Wise mobile solutions
[email protected]

+972-9-9581711 (116)
+972-67-340014

::..
It is far more impressive when others discover your good qualities without your help.
		-- Miss Manners