17:58 <  deuce868> so Doctrine_Resource is a web based db connection in essence?
17:58 <   jonwage> deuce868: sort of..
17:58 <  deuce868> what's the diff between this and implementing the code on the server side like you would normally do with an API?
18:00 <   jonwage> deuce868: well, the difference is that when you use this you can remotely access all of the data and models on the server, without actually having any of the code there
18:00 <  deuce868> well, you have to have the docrine code there thought right?
18:00 <   jonwage> it gets all the information via http and dynamically handles everything..
18:00 <   jonwage> For example, here is how i am going to use, and why I needed it
18:01 <   jonwage> I have a project where my client has a internal network of servers running in their office, one of the servers has a sybase database on it
18:02 <   jonwage> We will setup doctrine on that server and connect it to the sybase db
18:02 <   jonwage> Yes, you have to have it on the server.
18:02 <  deuce868> right, but is it with multiple clients or something? Any reason to not just open the db port to the client IP?
18:03 <   jonwage> So, we will have our actual web application sitting on another server somewhere that will have the Doctrine_Resource_Client on it and it will connect to the Doctrine_Resource_Server via a http url..
18:03 <   jonwage> and with the Doctrine_Resource_Client i can use all the Doctrine models and run DQL queries like i normally would..
18:03 <     webfx> heh just catching this stuff about resource_client .. that's friggin insane                          
18:03 <  deuce868> right, but if you had doctrine on the web server with access to the db via IP address it'd be less overhead                                                                                                                  
18:03 <   jonwage> deuce868: the server where the web application sits is not on the internal network..
18:04 <     webfx> i will actually use that for my next project                                                         
18:04 <   jonwage> The internal network is not sufficient to host the database AND the web application
18:06 <   jonwage> deuce868: it would be rediculously slow connecting to a db connection over a external ip address     
18:07 <   jonwage> i am not even sure if that is possible..i know it is not practical :)
18:07 <  deuce868> but you're doing the same thing over http...why is it slow? I have a ssh tunnel to our work test db I access from across the country
18:07 <  deuce868> well, I can tell you it's often done and done via the network since that's easier to secure, monitor, and control
18:08 <  deuce868> I see where you going and I guess without ssh tunnels or a vpn I can kind of see it                  
18:11 <   jonwage> deuce868: well, i think https is a lot easier to support network-wise than some sort of ssl tunnel to make a db connection.
18:11 <   jonwage> And I am not too sure about speed and scaling of something like that
18:12 <   jonwage> deuce868: but the idea is also that we can write clients in other languages to talk to Doctrine_Resource_Server, and then people can use Doctrine/DQL in other languages..
18:12 <   jonwage> And it is also like an instance api..
18:13 <  deuce868> http://www.linuxfocus.org/English/May2001/article202.shtml
18:13 <  deuce868> go down to ssh and mysql
18:13 <  deuce868> jonwage: no, I see your point now. Just didn't think of it because I've always seen the issue worked around other ways
18:14 <   jonwage> ya...it is more than how i am using it..
18:14 <    lsmith> webfx: hmm odd
18:14 <   jonwage> what i am using it for could be easily solved with your solution too
18:14 <   jonwage> but other popular orms have similar functionality to this
18:14 <   jonwage> what i am using it for could be easily solved with your solution too
18:14 <   jonwage> but other popular orms have similar functionality to this
18:14 <   jonwage> ActiveRecord in rails has ActiveResource :)