Hi all,
I'm just testing out the eval. of Smart Fox 1.61 and we were testing out the bluebox functionality.
We seem to be getting an error on the client side when the server responds to a POST through bluebox:
TypeError: Error #1091: XML parser failure: Unterminated CDATA section.
at it.gotoandplay.smartfoxserver::SmartFoxClient/xmlReceived()
at it.gotoandplay.smartfoxserver::SmartFoxClient/handleMessage()
at it.gotoandplay.smartfoxserver::SmartFoxClient/handleHttpData()
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at it.gotoandplay.smartfoxserver.http::HttpConnection/handleResponse()
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/onComplete()
It seems as though the response is being truncated. Is there a restriction on the size of the message/data which bluebox can handle? and if so, is this something that's configurable?
restriction on message/data size when going through bluebox
-
- Posts: 8
- Joined: 02 Apr 2008, 21:21
Hi,
there is no message size limit in the BlueBox but the server has a limit on the maximum size of incoming messages.
However this seems the opposite case, when the server sends data back to the client.
Could you give me more details about the message that you would expect when the error is fired?
Thank you
there is no message size limit in the BlueBox but the server has a limit on the maximum size of incoming messages.
However this seems the opposite case, when the server sends data back to the client.
Could you give me more details about the message that you would expect when the error is fired?
Thank you
-
- Posts: 8
- Joined: 02 Apr 2008, 21:21
I think we found what the problem was. We have embedded /n (newlines) within the data that we're sending back to the client. Unfortunately, SmartFoxClient.as is using that as a delimiter (function handleHTTPData) which causes it to prematurely terminate the message and hence causing the error mentioned above.
Is there anyway that this behavior can be modified by gotoandPlay? It's tough to guarantee that all data sent to the client will never contain any newlines.
Is there anyway that this behavior can be modified by gotoandPlay? It's tough to guarantee that all data sent to the client will never contain any newlines.
Hi,
there could be a problem with the url-encoding of the parameters. Are you using the AS 2.0 API ?
Sure, just let me know which API version do you use.
Thanks
there could be a problem with the url-encoding of the parameters. Are you using the AS 2.0 API ?
Is there anyway that this behavior can be modified by gotoandPlay? It's tough to guarantee that all data sent to the client will never contain any newlines.
Sure, just let me know which API version do you use.
Thanks
-
- Posts: 8
- Joined: 02 Apr 2008, 21:21
-
- Posts: 8
- Joined: 02 Apr 2008, 21:21
-
- Posts: 8
- Joined: 02 Apr 2008, 21:21
I didn't recall this immediately but the BlueBox can send 1 or more messages in one shot during a polling event.
As a separator for messages we chose to use the "\n" (new line character), so that's why you get broken data when you send that character within a single message.
As a workaround you could filter that character out or, if you really need to use it, encode it when sending the message and decode it back in the client. You could for example substitute it with a "$n" symbol or a similar combination.
I have added this to the fixes-list: we'll introduce a configurable separator character in order to avoid these problems in the future.
Hope it helps
As a separator for messages we chose to use the "\n" (new line character), so that's why you get broken data when you send that character within a single message.
As a workaround you could filter that character out or, if you really need to use it, encode it when sending the message and decode it back in the client. You could for example substitute it with a "$n" symbol or a similar combination.
I have added this to the fixes-list: we'll introduce a configurable separator character in order to avoid these problems in the future.
Hope it helps
-
- Posts: 8
- Joined: 02 Apr 2008, 21:21
Who is online
Users browsing this forum: No registered users and 37 guests