Re: [WebDNA] Talklist Archive & Twitter

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 102932
interpreted = N
texte = > I am positive that "user" and "pass" are correct because > I can login to twitter using them...can anybody see any > obvious syntax mistakes or omissions? Dan, when I tried your code in Firefox it said "This method requires a POST" but you're using GET so maybe that's the problem. --------------------------------------------------- By the way, has anyone done any Twitter Streaming API work with WebDNA? Personally don't think it's going to work at all -- because my understanding is that WebDNA won't do a thing with the data it receives via tcpconnect until it the source server closes the connection. That's how tcpconnect knows when to stop receiving data, isn't it? I mean, doesn't WebDNA simply hold the connection open until the source server closes it? This is my theory in the absence of documentation explaining how tcpconnect works. Unfortunately streaming data never ends, which means the source server never closes the connection, and therefore I think this will prevent WebDNA from ever doing anything with the partially transmitted data. I'm afraid this limitation may become a negative for WebDNA now that so many websites are being tied into streaming data systems like Twitter and Facebook so easily with other apps. Nevertheless I'm still hoping someone has attempted to use WebDNA with Twitter's Streaming API and can report his/her success or failure? Or perhaps someone at WSC who knows how tcpconnect actually works and can tell me if my theory is correct? Sincerely, Ken Grome Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Talklist Archive & Twitter ("Brian Harrington, Broker" 2009)
  2. Re: [WebDNA] Talklist Archive & Twitter (Donovan Brooke 2009)
  3. Re: [WebDNA] Talklist Archive & Twitter (Patrick McCormick 2009)
  4. Re: [WebDNA] Talklist Archive & Twitter (Donovan Brooke 2009)
  5. RE: [WebDNA] Talklist Archive & Twitter ("Michael A. DeLorenzo" 2009)
  6. Re: [WebDNA] Talklist Archive & Twitter (Tom Duke 2009)
  7. RE: [WebDNA] Talklist Archive & Twitter ("Michael A. DeLorenzo" 2009)
  8. Re: [WebDNA] Talklist Archive & Twitter (Tom Duke 2009)
  9. Re: [WebDNA] Talklist Archive & Twitter ("Dan Strong" 2009)
  10. RE: [WebDNA] Talklist Archive & Twitter ("Tana Adams" 2009)
  11. Re: [WebDNA] Talklist Archive & Twitter (Kenneth Grome 2009)
  12. Re: [WebDNA] Talklist Archive & Twitter (Tom Duke 2009)
  13. Re: [WebDNA] Talklist Archive & Twitter ("Dan Strong" 2009)
  14. Re: [WebDNA] Talklist Archive & Twitter (Stuart Tremain 2009)
  15. Re: [WebDNA] Talklist Archive & Twitter ("Dan Strong" 2009)
  16. Re: [WebDNA] Talklist Archive & Twitter (Kenneth Grome 2009)
  17. Re: [WebDNA] Talklist Archive & Twitter ("Dan Strong" 2009)
  18. RE: [WebDNA] Talklist Archive & Twitter ("Tana Adams" 2009)
  19. Re: [WebDNA] Talklist Archive & Twitter ("Dan Strong" 2009)
  20. Re: [WebDNA] Talklist Archive & Twitter ("Dan Strong" 2009)
  21. Re: [WebDNA] Talklist Archive & Twitter ("Dan Strong" 2009)
  22. Re: [WebDNA] Talklist Archive & Twitter ("Dan Strong" 2009)
  23. Re: [WebDNA] Talklist Archive & Twitter (Donovan Brooke 2009)
  24. [WebDNA] Talklist Archive & Twitter ("Tana Adams" 2009)
> I am positive that "user" and "pass" are correct because > I can login to twitter using them...can anybody see any > obvious syntax mistakes or omissions? Dan, when I tried your code in Firefox it said "This method requires a POST" but you're using GET so maybe that's the problem. --------------------------------------------------- By the way, has anyone done any Twitter Streaming API work with WebDNA? Personally don't think it's going to work at all -- because my understanding is that WebDNA won't do a thing with the data it receives via tcpconnect until it the source server closes the connection. That's how tcpconnect knows when to stop receiving data, isn't it? I mean, doesn't WebDNA simply hold the connection open until the source server closes it? This is my theory in the absence of documentation explaining how tcpconnect works. Unfortunately streaming data never ends, which means the source server never closes the connection, and therefore I think this will prevent WebDNA from ever doing anything with the partially transmitted data. I'm afraid this limitation may become a negative for WebDNA now that so many websites are being tied into streaming data systems like Twitter and Facebook so easily with other apps. Nevertheless I'm still hoping someone has attempted to use WebDNA with Twitter's Streaming API and can report his/her success or failure? Or perhaps someone at WSC who knows how tcpconnect actually works and can tell me if my theory is correct? Sincerely, Ken Grome Kenneth Grome

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

PSC recommends what date format yr 2000??? (1997) NT Version on IIS 4.0 (1997) SmithMicro Help! -- Can't access WebCatalog Admin! (2001) No luck with taxes (1997) Safari browser and WebDNA set-cookies (2003) WebMerchant crashing and other WebMerchant problem (2000) select multiple (1997) A Global Variable (1997) WebCat2 - [format thousands] (1997) Virtual hosting and webcatNT (1997) WC Database Format (1997) Pithy questions on webcommerce & siteedit (1997) More than one db with the same namn (was: WC2f3) (1997) [WebDNA] El Capitan (2017) how to check for no value while using [URL] to prevent cr (1999) Who is doing sign-ups-got it (1998) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) Attention SMSI - DOCS Error (2004) WebCat2 several catalogs? (1997) WebCatalog Use Question (1997)