Bug 2 is valid, can not reopen, so opening new bug, pinta always sends amfphp as destination, which causes problems

carlosg2 / pinta

Automatically exported from code.google.com/p/pinta

0 stars 0 forks source link

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago


I can provide plenty of logs. Pinta will only talk to my blazeds setup if I set 
the destination name in blazeds to amfphp.

Original issue reported on code.google.com by daniel.a...@gmail.com on 21 Aug 2010 at 3:05

GoogleCodeExporter commented 9 years ago

Pinta definitely seems to be hardcoding amfphp.  I can't connect to any of our 
services either.

Original comment by feise...@gmail.com on 31 Aug 2010 at 4:49