That isn't a concern for this application, especially over wifi. Thanks for the pointers… I'll try and check it all out tomorrow.sturgis wrote: It would get old to have to send a huge file every sync.
Socket Rience
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: Socket Rience
Re: Socket Rience
Ok… I have this working over http to the point of exchanging data between mobile and desktop devices. Now to implement the file transfer stuff, but this looks like it is going to work.
Thanks all for the suggestions.
Thanks all for the suggestions.
Re: Socket Rience
Yay! No, seriously, Yay! That's great news.
Did you end up using rev on rockets for the server end?
Did you end up using rev on rockets for the server end?
Re: Socket Rience
No. It appeared to be serious overkill… although I did start out using bits and pieces from it.
All I really need is an initial handshake confirmation (which I now have), and then the ability to post the database from the client and receive an updated copy as a reply. I still haven't decided whether I will just be exchanging info in the way of updated records to both sides, or transferring the entire database to the server, updating it there, and sending it back to the client.
I am guessing that, considering the size of the database file, it would be much simpler to simply transfer the entire file back and forth.
Yay indeed!
All I really need is an initial handshake confirmation (which I now have), and then the ability to post the database from the client and receive an updated copy as a reply. I still haven't decided whether I will just be exchanging info in the way of updated records to both sides, or transferring the entire database to the server, updating it there, and sending it back to the client.
I am guessing that, considering the size of the database file, it would be much simpler to simply transfer the entire file back and forth.
Yay indeed!
Re: Socket Rience
Hi rrBUSS9EE
Did you get this working? I think I have a solution..
I haven't had time to debug your code, but I do have a solution working with a Desktop RunRev Server (using accept connections...) and iOs devices using rreSocket to sync with the server from iOs devices. I have SQLite running on the Desktop Server, and on the iOs devices, and I use timestamped records to synchronize between them
No Dropbox, no webserver - just all sockets
If you are interested,we can chat offline, and work out details - there are many tricky issues - I don't have a "solution" to post, but I would be happy to work alongside someone doing the same things. email me: info at mobss dot com
r
Did you get this working? I think I have a solution..
I haven't had time to debug your code, but I do have a solution working with a Desktop RunRev Server (using accept connections...) and iOs devices using rreSocket to sync with the server from iOs devices. I have SQLite running on the Desktop Server, and on the iOs devices, and I use timestamped records to synchronize between them
No Dropbox, no webserver - just all sockets
If you are interested,we can chat offline, and work out details - there are many tricky issues - I don't have a "solution" to post, but I would be happy to work alongside someone doing the same things. email me: info at mobss dot com
r
Re: Socket Rience
Realize this is an old thread but wondering if you ever got this to work?
Looking at a project right now where I need to use iOS Client Sockets via this external and would love to confirm it works before going through the paces!!
EDIT - I see above you seem to have got this working, if you are willing to share with me the how to I would greatly appreciate it!
Looking at a project right now where I need to use iOS Client Sockets via this external and would love to confirm it works before going through the paces!!
EDIT - I see above you seem to have got this working, if you are willing to share with me the how to I would greatly appreciate it!
Re: Socket Rience
rresockets works fine Nakia. The original code had a few issues that it looks like nobody corrected. Namely the initial write to the socket didn't have a callback message parameter. You need to wait for the callback then read from the socket with another callback message that has the data. The original code also missed the second param on the read which in most cases you want to be 0 because that tells the external to read all available data. Check the demo for an example.
Cheers
Monte
Cheers
Monte
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/
Re: Socket Rience
Thanks monte..
For some reason the demo stack in the folder is corrupt.
I might download it again from mergExt and see if I can get it to
Load..
For some reason the demo stack in the folder is corrupt.
I might download it again from mergExt and see if I can get it to
Load..