...snip... > So, you have a small webserver running on some device hooked to the > network. The stuff on your device uses uClibc without wchar support. > Now you want to write a browser application with GWT, i.e. an > administration interface for this device. Am I close? You are almost there !!
> Personally, I think you should let your webserver escape und unescape > the \0 bytes before handing the data to your back-end application. > This would make your device more robust and probably safer. Would you elaborate more on this ? What exactly my webserver should do ? > However, if you want to do this inside your client app before sending it over > the network you can use URL.encode() or regular expressions. > > http://google-web-toolkit.googlecode.com/svn/javadoc/1.5/com/google/g...)http://google-web-toolkit.googlecode.com/svn/javadoc/1.5/com/google/g...) > Will take a look. > > I was hoping wctomb would covert a unicode char which in normal case > > if treated as single byte char sequence might have '\0' in it, to a > > multi byte sequence(might be more than 2 bytes if required) which will > > not have '\0' but correct me if i am wrong. > > No, wctomb(3) just converts your \0 wide character to one \0 byte. hmm .. So it won't solve null termination problem i think. Then wctomb is not what i need. Thanks a lot for all the help provided so far. -Rohit --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
