Honestly filesystems suck, there's so many gotchas from a security perspective, when all you really want is to pipe binary data in this side, and out the other side. I implemented an IRC bot in a few hours in javascript one day /10/17 · 12/20/18 Update: Removed a check for WSUS cmdlets that prevented the script from working on R2 and the ReSyncUpdates from the WSUS standalone config file. 12/10/18 Update: Fixed a configuratio /05/22 · Dating Apps Suck and This App Is Our Last Hope By Glen Smith May 22, to be an inclusive community for everyone. You can pick to only view males or only females or both (where’s the non-binary option?). You can also like, “just be friends” with someone. so he developed this while attending business school in (shoutout to
Spore (Video Game) - TV Tropes
dominiek 49 days ago [—]. I never thought I would say this, but I actually implemented an FTP server in This was needed to support firmware updates to specific hardware Electric Vehicle charging stations. Apparently embedded software developers choose FTP whenever a spec doesn't specify how binary file transfers should work. It was kind of amusing getting FTP to work in a modern cloud environment. I run a single Kubernetes pod with a Node. js based FTP server optimized for one thing: Transferring files between FTP and Google Cloud Storage.
A series of ports are specified in the Docker file to enable passive FTP transfers. Even more amusing was the number of varieties in which FTP was implemented by different hardware manufacturers. I regularly had to dive into the FTP libraries to add support for crazy edge cases tcpflow in kubectl exec -it is your friend!
The latest curve ball I received this week is that a certain firmware version of a Qualcomm modem chip cannot deal with the size of binary option that suck school IP packets coming from our FTP server Fun stuff!
tpmx 49 days ago [—]. Implementing an FTP server from scratch that had to be compatible with lots of clients in was an interesting choice. Just to have it in javascript? Perhaps security-motivated? There are probably battle tested implementations in e. Python, Java or other safe-ish languages to build on?
I learned this lesson in the mid 90s when fixing client compatibility bugs in an FTP server module we had built in an interpreted language, because, how hard could it be klodolph 49 days ago [—].
My experience there aren't a ton of choices in this space. There are a few FTP servers designed to power B2B backend services. Many of the options are designed only to provide access to the local filesystem. axiolite 49 days ago [—], binary option that suck school. The "local filesystem" doesn't have to be a local file system.
It's just a good, common abstraction useful for interoperability. Why not "rclone mount" your Google Drive, or use some other FUSE based file system to get easy interoperability between legacy FTP servers and modern storage options? klodolph 48 days ago [—]. I don't think I agree that the local filesystem is a good, common abstraction. It's a serviceable abstraction most of the time, and a terrible abstraction at other times.
This isn't just some contrarian stance I'm taking--I've just spent too much time fighting with filesystem semantics on too many OSs. Going through FUSE is, in my mind, binary option that suck school, a last resort. rectang 49 days ago [—], binary option that suck school. How much better have we gotten at specifying protocols? Have we binary option that suck school how to make protocols less ambiguous and less susceptible to crazy edge cases which make it burdensome to implement support in practice once there are lots of sloppy implementations in the field?
aidenn0 49 days ago [—]. in many cases the misbehaving clients and servers are obviously wrong, but Postel's law means they "worked for me" when the developer tested it 10 years ago before abandoning it. The FTP protocol got a lot of cruft added to it that modern clients don't implement e. any transfer mode other than stream. FTP over TCP predates NATs and firewalls, which caused a lot of problems as well. FTP was designed for human-readable, not machine-readable output.
In particular the output of a LIST command is woefully underspecified. I think 1 is the biggest issue for long-term viability of protocols. Not following Postel's law is a recipe for death same reason why it's suicide for a browser to unilaterally untrust a major CA; any site that doesn't work in browser X is assumed to be browser X's faultbut following Postel's binary option that suck school is a recipe for undocumented de-facto standards with crazy edge cases.
Thanks, wonderful reply! I see that there's been binary option that suck school debate over the applying Postel's Law, a. The posture this statement advocates promotes interoperability in the short term, but can negatively affect the protocol ecosystem over time.
For a protocol that is actively maintained, the robustness principle can, and should, be avoided. It seems that you need both for the protocol to be unambiguously, fully specified, and for popular implementations to avoid applying Postel's Law! But we've seen how market forces conspire to work against that. winrid 49 days ago [—]. Just curious on the motivation. Why not run a regular Binary option that suck school server and have your application periodically look for new files to process?
For horizontal scaling, you just take a distributed lock on the file name. admax88q 49 days ago [—]. That honestly sounds more complicated. FTP isn't that difficult of a protocol, especially if you only need to support one known client, you can take all sort of shortcuts. Now you gotta administrate an FTP server that's probably written for classic UNIX single server usage, gotta handle filesystem permissions, gotta somehow hook up your distributed locks to the filesystem, sanitize filenames for your chosen filesystem.
Honestly filesystems suck, there's so many gotchas from a security perspective, when all you really want is to pipe binary data in binary option that suck school side, and out the other side. I implemented an IRC bot in a few hours in javascript one day. Those classic IETF text based protocols are actually really fun and easy to implement, especially in a language that makes binary option that suck school safe and easy i.
not C. I could easily see figuring out all the deployment concerns around integrating with an existing FTP server end up taking way longer than just integrating the subset needed for this use case. stjohnswarts 49 days ago [—]. Strings in c aren't that bad with stuff like bstring or glib. Just gotta be careful with deallocations so you don't get leaks. Much better than all the security issues with std strings.
recursive 49 days ago [—]. Active mode is pretty weird. Coordinating a single client across two ports sounds difficult to me, but I've never implemented it. If that's not a difficult protocol, then what is? tuwtuwtuwtuw 49 days ago [—]. Http3, IMAP, Caldav and MAPI? Cordinating a client across two ports sounds trivial compared to for example properly implementing client and server versions of IMAP search commands when no client or server follows the specification.
pixl97 49 days ago [—]. Until you realize that the two ports commonly involve dealing with middleware that cant handle it properly.
tuwtuwtuwtuw 48 days ago [—]. You will have similar issues with other protocols as well. I have seen physical bandwidth limiters, windows drivers, binary option that suck school, corrupt winsock LSPs etc mess with IMAP traffic.
The lock would be handled by something like Redis or a DB. But yeah, binary option that suck school, if you only need to support one client, I can see the reasoning. It would never have flied at any of the places I've worked, though, having to support tons of clients. Yeah totally I hear you. If you have to support many external clients using an existing ftp implementation makes lot more sense. I had considered this, but decided against this for a couple of reasons: - Scaling requirements are relatively low.
Even though we're dealing with 10 thousands of devices, the amount of firware updates at a given time to those devices is minimal. Our main scaling challenges are around OCPP over websockets, binary option that suck school.
Story for another day. Essentially, I'm using FTP as a throwaway here, binary option that suck school. If you think through this you can imagine it would be quite a lift to accomplish this with an existing FTP server. They describe why, tons of edge cases from poorly implemented ftp clients, they needed full control over the protocol to handle weird edge cases because of multiple embedded clients.
meritt 49 days ago [—]. Because nodejs kubernetes modern binary option that suck school. The main reason for using Node. js is because the rest of our stack is Node. io We use MongoDB as persistence and have existing wrappers for dealing with Google Cloud Storage. Since it's an isolated service we could've used a different implementation language. In our case Node.
Binary Options Trading is Dead. What happened? ��
, time: 10:00IQCent Review - Read What 14 People Say
blogger.com is available globally. Access and membership requires all visitors to conform to the laws of their own country as well as the Site's User blogger.com may be some areas of the Site that become unavailable due to the conditions and guidance in effect at that time Armless Biped: An option, and often what you start the Creature stage with. Artistic License – Biology: To be expected in a game more focused on being cool and fun. All of the Epic creatures are carnivores or omnivores, probably to make them more of a threat to the player, even though the largest land animals in real life have been herbivores /10/17 · 12/20/18 Update: Removed a check for WSUS cmdlets that prevented the script from working on R2 and the ReSyncUpdates from the WSUS standalone config file. 12/10/18 Update: Fixed a configuratio
No comments:
Post a Comment