It would be nice if AXIOM was standalone, but on the other hand if the code already exists in APR then it will be quicker to re-use it.

I suggest that we go ahead and use APR. If it becomes too big a dependency then we can always add our own hash+stack later and refactor AXIOM to use it.

Thoughts?

Paul



On 9/29/05, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
I am running into several problems while trying to implement the
XMLStreamWriter API for guththila.
Mainly, we need a stack (to push and pop elements), and a hash map (to
validate namespaces)

I cannot use the current stack defined in Guththila as I cannot store
generic data in it.
I have both stack (i.e. push/pop arrays) and hash map in APR, but I am
wondering if the use of APR in guththila would be a good idea.
Otherwise I would have to write a stack and a hash map (stack is simple
but not the hash map :( )

Is it OK if I use APR for Guththila XMLStreamWriter?

Thoughts please...
P.S. I am kind of stuck without XMLStreamWriter in Guththila as we must
have it to serialize OM.

Thanks,
Samisa...

Dinesh Premalal wrote:

> Hi,
>
> On 9/28/05, *Samisa Abeysinghe* <[EMAIL PROTECTED]
> <mailto: [EMAIL PROTECTED]>> wrote:
>
>     Hi Dinesh,
>         Any plans to implement the writer API in guththila?
>         We are very badly in need of a writer API for seralizing in AXIOM
>
>
> since writer api need for implement serializing in AXIOM I will look
> on it.
>
> thanks,
> Dinesh
>
>     Thanks,
>     Samisa...
>
>
>
>
> --
> W.Dinesh Premalal
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> http://www.cse.mrt.ac.lk/~premalwd/
> <http://www.cse.mrt.ac.lk/%7Epremalwd/>



Reply via email to