Re: [SOAP] Error fetching headers
| From: | Andrey Hristov | Date: | Tue, 04 Jun 2002 10:54:43 +0000 |
| Subject: | Re: [SOAP] Error fetching headers | ||
| References: | 1 | Groups: | php.soap |
| Request: | Send a blank email to php-soap+get-77@lists.php.net to get a copy of this message | ||
> > I have another problem with the extension. It is not possible to
transport
> > Cyrillic symbols from the server to the client. Probably this is not
only
> > problematic when dealing with cyrillic but probably with other
non-english
> > symbols.
>
> Are you sure about this?.. I use the extension for full utf-8 support I
> transport all sorts of wierd symbols. I even use mb_string to manipulate
utf-8
> comming from a utf-8 db.
Yes, I'm sure. I've faced this after extracting cyrillic symbols from MySQL
and tried to
transport. After then I just tried to return "Аз се казвам Андрей"; and
the
things went to the hell.
>
> > Last but not least there is problem with the integer indexes of arrays.
> > In case all keys are integers but not sequent and greater than 0. After
> > transporting them the array is reordered starting from 0 to count()-1. I
> > think that the problem is in the server part. On the other hand if to
the
> > same array is added a value with string key than the nothing changes.
I've
> > experienced similar problems with array_slice() and some other functions
> > that are "naughty" enough to change the keys. In my case the keys are
> > timestamp from nowadays
>
> This is true... For this to work it would have to handle sparse array
> encoding. Which it "will" do someday. There are some other things that it
> doesn't do with arrays right now ither.
>
> To get around this can you cast your timestamps as strings.. Then it will
treat
> the array as a hashtable and you can get what you are looking for.
>
casting to strings does nothing -> $ret_ar["$timestamp"] is not different
than $ret_ar[$timestamp]
the result is the same. If I use $ret_ar["_$timestamp"] then strings are
returned.
Best regards,
Andrey Hristov