I have a FLEX 3 frontend that worked fine in FlashPlayer 9. But now that I've upgraded to FlashPlayer10, the ?_method=PUT/DELETE hack is not working anymore. All those requests show up as a POST on the backend now. I did some reading and it sounds like I need to use as3httpclientlib AND run a socket policy server to give access to port 80 (or any other port) in order to use as3httpclientlib. So my question is: are you freakin kidding me? How is it that, in earlier versions of Flex/flash player, all I had to do was add a simple string ("_method=") to the url. But now I have to do the hokey pokey AND turn my self around? Really? Please someone tell me that I've got this all wrong, and that _method= is, in fact, still supported. Otherwise, its BYE BYE FLEX/FLASH PLAYER - NEVER AGAIN!
I understand you very much, my friend, just had similar noise with authentication headers in new one Security Policy from Adobe. Anyway, if you'll share your code, maybe I could help you, because your goal is not clearly explained in your post, Buddy. So let me know please, cause java sandbox and silverlight are not the better way in this case. But maybe some javascript stuff could save our time.
Related
I try to synchronize VR scene using GunDB.
In order to experiment it, I put a few data in GunDB.
But I got this warning.
storage warning
I use IndexedDB, and I can keep going it with hitting 'allow'
But I'm wondering why it uses too much storage!!!!!
setInterval(putLocation, Math.ceil(1000 / 50));
// putLocation
obj.get('attributes').get('position').put(object.attributes.position);
It updates data every 200ms in the same node. (object.attributes.position)
please let me know how could I fix it.
Thank you.
#huhsame 1.2GB for VR scene data? That seems suspicious.
By chance is this in Safari?
Safari has a known bug (#go1dfish found this) where it creates run-away storage accumulation (with or without gunDB) that gets triggered if its file descriptor is left open too long.
Could you see if the same thing happens in Chrome? If it does, it is a GUN bug then.
If it is just Safari, we tried to add code that would reset/reopen Safari's IndexedDB instance every 15 seconds, and have had success so far with that approach.
However, clearly, either Safari has changed something, or that workaround is no longer viable, so we'll need to figure something new out.
I understand Safari is very important because of iOS, it is just unfortunate that Safari lags behind on several very serious and important fronts (WebRTC, IndexedDB, & WebM). There is only so much our team can do to work around these bugs until Safari is more standards compliant. But where we can workaround, we will.
#marknadal
thanks for your answer.
and sorry I am late.
I tested it on Chrome and Safari after clearing storage.
after 30 minutes, Chrome used about
1MB,
and on the Safari, I did not find the usage panel but there is no pop-up for warning like the previous one.
I guess it was total data since September when I had started this experiment.
but it's just my opinion.
And I am still wondering that users should delete data in WebStorage regularly?
please answer me.
I'm completely new to UPnP as a protocol, but I'm hoping to use it to transfer files from a Sony Camera to an iOS app I'm working on. So far I have SSDP discovery setup, I can read the UPnP client's services, search through folders and access file names, but the final hurdle which I'm stuck on is how to actually download/transfer the files once I'm able to list them!
What I end up getting is the below:
<item id="04_02_0624600856_000001_000001_000000" restricted="1" parentID="03_01_0624600856_000001_000000_000000">
<dc:title>DSC05076.ARW</dc:title>
<upnp:class>object.item.imageItem.photo</upnp:class>
<dc:date>2018-08-23T12:24:21</dc:date>
<res protocolInfo="http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_SM;DLNA.ORG_CI=1">http://192.168.122.1:60151/SM_DSC05076.ARW?%2104%5f02%5f0624600856%5f000001%5f000001%5f000000%21http%2dget%3a%2a%3aimage%2fjpeg%3aDLNA%2eORG%5fPN%3dJPEG%5fSM%3bDLNA%2eORG%5fCI%3d1%21%21%21%21%21</res>
<res protocolInfo="http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_LRG;DLNA.ORG_CI=1">http://192.168.122.1:60151/LRG_DSC05076.ARW?%2104%5f02%5f0624600856%5f000001%5f000001%5f000000%21http%2dget%3a%2a%3aimage%2fjpeg%3aDLNA%2eORG%5fPN%3dJPEG%5fLRG%3bDLNA%2eORG%5fCI%3d1%21%21%21%21%21</res>
<res protocolInfo="http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_TN;DLNA.ORG_CI=1">http://192.168.122.1:60151/TN_DSC05076.ARW?%2104%5f02%5f0624600856%5f000001%5f000001%5f000000%21http%2dget%3a%2a%3aimage%2fjpeg%3aDLNA%2eORG%5fPN%3dJPEG%5fTN%3bDLNA%2eORG%5fCI%3d1%21%21%21%21%21</res>
I would (With my naive experience of simple HTTP APIs) then expect to simply be able to download the file in question by hitting:
http://192.168.122.1:60151/SM_DSC05076.ARW or similar (I'm assuming I have to change this URL slightly as the file is listed as image/jpeg rather than RAW?
Whatever combination I try of the full res object, snipping bits, decoding the url e.t.c. I always get a 404 response when trying to visit the URL in question. Is there something more complex I need to do here? Or something simple that I'm missing?
Thanks in advance!
The problem here was that I was using a url from a previous session. It turns out that the urls change between connection sessions, which is why I was getting a 404.
Lesson learned: UPnP is highly dynamic, and you can’t rely on caching images under their access MRL!
We have been using the following library for months:
https://unpkg.com/react#15.3.0/dist/react.min.js
Yes - I know we can just reference 15.3 and get the URL rewrite to the latest, but they released a breaking change. That's another issue for another day. Don't get distracted.
Yesterday this simply stopped working. You'll notice that if you load the URL mentioned, that the file is TRUNCATED. Simply cuts off. This made everything we use react with break. Interestingly, if you go to the following URL (without the .js extension) - things work.
https://unpkg.com/react#15.3.0/dist/react.min
My question is - what the heck happened? Why did the URL we've been using for 8 months suddenly stop working, and who can we get to fix it. In the interim, we had a copy locally that we've started referencing (which we probably should have been doing to begin with, since we don't want the automatic upgrade). When things like this happen, who do you inform?
I'm not sure you'll find the answer as to why this file is no longer working here but based off of the website you could reached out to the creator on twitter: https://twitter.com/mjackson
On the website it says:
SUPPORT
unpkg is a free, best-effort service and cannot provide any uptime or
support guarantees.
i.e. you should probably only use this link if you are messing around with a small project and shouldn't be used for any website where you actually care about the uptime of the site.
This is a very specific problem, but I'm experiencing an issue where I have 0 knowledge and experience.
I have the Flags Module 7.x-3.7 installed on Drupal 7.44. I was able to set up an 2 actions that send emails when a user activates a flag.
Now, all of a sudden I an unable to do so. The entire system hangs indefinitely whenever I: A) Click on the “edit” link for any flags the result in an email being sent or B) Try to create a new action using “Send e-mail” as the action.
I tried removing the modules, toggling other modules… the usual fare. I’m not massively familiar with Drupal, so the intereconnected workings have me a bit nervous to mess around. I am, however, familiar with PHP and MYSQL and have access to the root, so I can investigate pretty much wherever.
So,does anyone have any idea what could be causing this issue? Why does it not move past a connecting icon and move to the new page when the links are clicked? It’s not even a WSOD as far as I can tell.Any other information you need, please feel free to ask. I’m not even sure what’s needed to troubleshoot a Drupal 7 site, honestly, but any Help would be appreciated.
Looks like the following line is causing an issue. It's in flag_actions.module, the function flag_actions_system_send_email_action_form(&$form, &$flag, $context):
$form['help']['basic'] = array(
'#markup' => theme('flag_tokens_browser', array('types' => array('flag', 'flag-action'))),
);
Commenting it out seems to solve the issue. I'd like to know WHY, and if it is safe to leave it commented out at the moment. Any ideas?
I would like to use magnific popup for a site which is still in development, but unfortunately nothing happens after the installation and adding the static content in my template.
No matter what i try no popup comes up.
If someone would like to help me i will provide access to the site.
Thanks a lot!
First thing to do:
look at your source code: does the 'link' show any sign of 'magnific popup' code?
Added classes? id?
Second: do you see any extra javascript and/or stylesheet that is added by the extension?
If you answer negative to 1 of these, the extension does not output anything. Sounds logic, but it is the first step. Is it a solution? Nope, it means your live just got a bit more worse, but hang in there !
If it does show any code from the ext: look at your console, are there any js errors occurred ? (if you don't know what console is, or (even worse) you work with IE) please read about chrome console of at least install Firefox with firebug.
My best beth would be a JS error...
Can it be possible that the ext itself does not work?
Does your php error logs tell you that the extension is behaving badly?
Do you see errors in the typoscript analyser (or whatever it's called to analyse the css_styled_content and other TS spaghetti )
If not, then no, it is not the ext.
Again, i'm betting my wive, three horses and a barrel of beer on JS erros.
Good luck mate !
ps: IF i'm wrong, i'm not sending you my wife by postal service. Loads of trouble last time. Nor the horses, same shizzle ..